linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ritesh Harjani (IBM)" <ritesh.list@gmail.com>
To: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org
Cc: Jan Kara <jack@suse.cz>, Christoph Hellwig <hch@infradead.org>,
	"Darrick J . Wong" <djwong@kernel.org>,
	Ojaswin Mujoo <ojaswin@linux.ibm.com>,
	"Ritesh Harjani (IBM)" <ritesh.list@gmail.com>
Subject: [RFCv2 0/8] ext2: DIO to use iomap
Date: Tue, 11 Apr 2023 10:51:48 +0530	[thread overview]
Message-ID: <cover.1681188927.git.ritesh.list@gmail.com> (raw)

Please find the series which moves ext2 direct-io to use modern iomap interface.

Here are some more details -
1. Patch-1: Fixes a kernel bug_on problem with ext2 dax code (found during code
   review and testing).
2. Patch-2: Adds a __generic_file_fsync_nolock implementation as we had
   discussed.
3. Patch-3 & Patch-4: Moves ext4 nojournal and ext2 to use _nolock method.
4. Patch-5: This is the main patch which moves ext2 direct-io to use iomap.
   (more details can be found in the patch)
5. Patch-6: Kills IOMAP_DIO_NOSYNC flag as it is not in use by any filesystem.
6. Patch-7: adds IOCB_STRINGS macro for use in trace events for better trace
   output of iocb flags.
7. Patch-8: Add ext2 trace point for DIO.

Testing:
=========
This passes ext2 "auto" group testing for fstests. There were no new failures
with this patches.


Ritesh Harjani (IBM) (8):
  ext2/dax: Fix ext2_setsize when len is page aligned
  libfs: Add __generic_file_fsync_nolock implementation
  ext4: Use __generic_file_fsync_nolock implementation
  ext2: Use __generic_file_fsync_nolock implementation
  ext2: Move direct-io to use iomap
  iomap: Remove IOMAP_DIO_NOSYNC unused dio flag
  fs.h: Add IOCB_STRINGS for use in trace points
  ext2: Add direct-io trace points

 fs/ext2/Makefile      |   2 +-
 fs/ext2/ext2.h        |   1 +
 fs/ext2/file.c        | 127 +++++++++++++++++++++++++++++++++++++++++-
 fs/ext2/inode.c       |  57 +++++++++++--------
 fs/ext2/trace.c       |   5 ++
 fs/ext2/trace.h       |  61 ++++++++++++++++++++
 fs/ext4/fsync.c       |  31 +++++------
 fs/iomap/direct-io.c  |   2 +-
 fs/libfs.c            |  43 ++++++++++++++
 include/linux/fs.h    |  15 +++++
 include/linux/iomap.h |   6 --
 11 files changed, 303 insertions(+), 47 deletions(-)
 create mode 100644 fs/ext2/trace.c
 create mode 100644 fs/ext2/trace.h

--
2.39.2


             reply	other threads:[~2023-04-11  5:22 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11  5:21 Ritesh Harjani (IBM) [this message]
2023-04-11  5:21 ` [RFCv2 1/8] ext2/dax: Fix ext2_setsize when len is page aligned Ritesh Harjani (IBM)
2023-04-11 14:29   ` Darrick J. Wong
2023-04-11  5:21 ` [RFCv2 2/8] libfs: Add __generic_file_fsync_nolock implementation Ritesh Harjani (IBM)
2023-04-11  5:27   ` Christoph Hellwig
2023-04-11 12:33     ` Matthew Wilcox
2023-04-11 15:12       ` Ritesh Harjani
2023-04-12 11:43       ` Christoph Hellwig
2023-04-12 14:02         ` Ritesh Harjani
2023-04-13  9:51         ` Christian Brauner
2023-04-11  5:21 ` [RFCv2 3/8] ext4: Use " Ritesh Harjani (IBM)
2023-04-11  5:21 ` [RFCv2 4/8] ext2: " Ritesh Harjani (IBM)
2023-04-11  5:21 ` [RFCv2 5/8] ext2: Move direct-io to use iomap Ritesh Harjani (IBM)
2023-04-11  5:46   ` Christoph Hellwig
2023-04-11 15:21     ` Ritesh Harjani
2023-04-12 11:43       ` Christoph Hellwig
2023-04-12 14:03         ` Ritesh Harjani
2023-04-11  5:21 ` [RFCv2 6/8] iomap: Remove IOMAP_DIO_NOSYNC unused dio flag Ritesh Harjani (IBM)
2023-04-11  5:27   ` Christoph Hellwig
2023-04-11  5:21 ` [RFCv2 7/8] fs.h: Add IOCB_STRINGS for use in trace points Ritesh Harjani (IBM)
2023-04-11  5:38   ` Christoph Hellwig
2023-04-11  5:21 ` [RFCv2 8/8] ext2: Add direct-io " Ritesh Harjani (IBM)
2023-04-11  5:38   ` Christoph Hellwig
2023-04-11 14:34     ` Darrick J. Wong
2023-04-11 15:11       ` Ritesh Harjani
2023-04-12 11:44         ` Christoph Hellwig
2023-04-12 14:07           ` Ritesh Harjani
2023-04-12 11:45 ` [RFCv2 0/8] ext2: DIO to use iomap Jan Kara
2023-04-12 14:10   ` Ritesh Harjani

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1681188927.git.ritesh.list@gmail.com \
    --to=ritesh.list@gmail.com \
    --cc=djwong@kernel.org \
    --cc=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=ojaswin@linux.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).