From: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
Jan Kara <jack@suse.cz>, Christoph Hellwig <hch@infradead.org>,
"Darrick J . Wong" <djwong@kernel.org>,
Ojaswin Mujoo <ojaswin@linux.ibm.com>,
Disha Goel <disgoel@linux.ibm.com>, Ted Tso <tytso@mit.edu>
Subject: Re: [PATCHv6 0/9] ext2: DIO to use iomap
Date: Fri, 21 Apr 2023 17:35:47 +0530 [thread overview]
Message-ID: <87edodigo4.fsf@doe.com> (raw)
In-Reply-To: <20230421112324.mxrrja2hynshu4b6@quack3>
Jan Kara <jack@suse.cz> writes:
> Hello Ritesh,
>
> On Fri 21-04-23 15:16:10, Ritesh Harjani (IBM) wrote:
>> Hello All,
>>
>> Please find the series which rewrites ext2 direct-io path to use modern
>> iomap interface.
>
> The patches now all look good to me. I'd like to discuss a bit how to merge
Thanks Jan,
> them. The series has an ext4 cleanup (patch 3) and three iomap patches
Also Patch-3 is on top of ext4 journalled data patch series of yours,
otheriwse we might see a minor merge conflict.
https://lore.kernel.org/all/20230329154950.19720-6-jack@suse.cz/
> (patches 6, 8 and 9). Darrick, do you want to take the iomap patches through
> your tree?
>
> The only dependency is that patch 7 for ext2 is dependent on definitions
> from patch 6
That's right. Patch 6 defines TRACE_IOCB_STRINGS definition which both
ext2 and iomap tracepoints depend upon.
> so I'd have to pull your branch into my tree. Or I can take
> all the iomap patches through my tree but for that it would be nice to have
> Darrick's acks.
>
> I can take the ext4 patch through my tree unless Ted objects.
Sure, we might have to merge with Ted's ext4 tree as well to avoid the
merge conflict I mentioned above.
>
> I guess I won't rush this for the coming merge window (unless Linus decides
> to do rc8) but once we settle on the merge strategy I'll push out some
Ok.
> branch on which we can base further ext2 iomap conversion work.
>
Sure, will this branch also gets reflected in linux-next for wider testing?
-ritesh
next prev parent reply other threads:[~2023-04-21 12:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 9:46 [PATCHv6 0/9] ext2: DIO to use iomap Ritesh Harjani (IBM)
2023-04-21 9:46 ` [PATCHv6 1/9] ext2/dax: Fix ext2_setsize when len is page aligned Ritesh Harjani (IBM)
2023-04-21 9:46 ` [PATCHv6 2/9] fs/buffer.c: Add generic_buffers_fsync*() implementation Ritesh Harjani (IBM)
2023-04-21 9:46 ` [PATCHv6 3/9] ext4: Use generic_buffers_fsync_noflush() implementation Ritesh Harjani (IBM)
2023-04-21 9:46 ` [PATCHv6 4/9] ext2: Use generic_buffers_fsync() implementation Ritesh Harjani (IBM)
2023-04-21 9:46 ` [PATCHv6 5/9] ext2: Move direct-io to use iomap Ritesh Harjani (IBM)
2023-04-21 9:46 ` [PATCHv6 6/9] fs.h: Add TRACE_IOCB_STRINGS for use in trace points Ritesh Harjani (IBM)
2023-04-21 15:56 ` Darrick J. Wong
2023-04-21 9:46 ` [PATCHv6 7/9] ext2: Add direct-io " Ritesh Harjani (IBM)
2023-04-21 9:46 ` [PATCHv6 8/9] iomap: Remove IOMAP_DIO_NOSYNC unused dio flag Ritesh Harjani (IBM)
2023-04-21 15:56 ` Darrick J. Wong
2023-04-21 9:46 ` [PATCHv6 9/9] iomap: Add DIO tracepoints Ritesh Harjani (IBM)
2023-04-21 15:56 ` Darrick J. Wong
2023-04-21 11:23 ` [PATCHv6 0/9] ext2: DIO to use iomap Jan Kara
2023-04-21 12:05 ` Ritesh Harjani [this message]
2023-04-21 15:40 ` Darrick J. Wong
2023-04-24 9:43 ` Jan Kara
2023-04-24 9:44 ` Jan Kara
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=87edodigo4.fsf@doe.com \
--to=ritesh.list@gmail.com \
--cc=disgoel@linux.ibm.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 \
--cc=tytso@mit.edu \
/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