From: "Darrick J. Wong" <djwong@kernel.org>
To: dsterba@suse.cz, Christoph Hellwig <hch@lst.de>,
Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: reduce memory allocation in the btrfs direct I/O path
Date: Mon, 9 May 2022 20:33:05 -0700 [thread overview]
Message-ID: <20220510033305.GB27137@magnolia> (raw)
In-Reply-To: <20220509184650.GA18596@twin.jikos.cz>
On Mon, May 09, 2022 at 08:46:50PM +0200, David Sterba wrote:
> On Sat, May 07, 2022 at 07:26:49AM +0200, Christoph Hellwig wrote:
> > On Fri, May 06, 2022 at 10:18:03AM -0700, Darrick J. Wong wrote:
> > > > The series is reasonably short so I'd like to add it to 5.20 queue,
> ^^^^
> Sorry, I meant 5.19, ie. the one that's about to start soon.
>
> > > > provided that the iomap patches get acked by Darrick. Any fixups I'd
> > > > rather fold into my local branch, no need to resend unless there are
> > > > significant updates.
> > >
> > > Hm. I'm planning on pushing out a (very late) iomap-5.19-merge branch,
> > > since (AFAICT) these changes are mostly plumbing. Do you want me to
> > > push the first three patches of this series for 5.19?
> >
> > Given that we have no conflicts it might be easiest to just merge the
> > whole series through the btrfs tree.
>
> Yeah, I'd rather take it via the btrfs tree.
Ah, *5.19*. Yes, this plan now sounds good to me!
(I had wondered, 5.20 seemed like an awfully long time to wait for
something as straightforward as that.)
--D
prev parent reply other threads:[~2022-05-10 3:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 16:23 reduce memory allocation in the btrfs direct I/O path Christoph Hellwig
2022-05-04 16:23 ` [PATCH 1/5] iomap: allow the file system to provide a bio_set for direct I/O Christoph Hellwig
2022-05-05 15:38 ` Darrick J. Wong
2022-05-04 16:23 ` [PATCH 2/5] iomap: add per-iomap_iter private data Christoph Hellwig
2022-05-05 8:06 ` Nikolay Borisov
2022-05-05 15:06 ` Christoph Hellwig
2022-05-05 15:41 ` Darrick J. Wong
2022-05-05 15:45 ` Christoph Hellwig
2022-05-05 16:32 ` Darrick J. Wong
2022-05-05 18:15 ` Christoph Hellwig
2022-05-05 18:18 ` Darrick J. Wong
2022-05-04 16:23 ` [PATCH 3/5] btrfs: add a btrfs_dio_rw wrapper Christoph Hellwig
2022-05-04 16:23 ` [PATCH 4/5] btrfs: allocate dio_data on stack Christoph Hellwig
2022-05-04 16:23 ` [PATCH 5/5] btrfs: allocate the btrfs_dio_private as part of the iomap dio bio Christoph Hellwig
2022-05-05 8:12 ` Nikolay Borisov
2022-05-05 15:07 ` Christoph Hellwig
2022-05-05 15:20 ` David Sterba
2022-05-05 15:52 ` David Sterba
2022-05-05 8:33 ` reduce memory allocation in the btrfs direct I/O path Nikolay Borisov
2022-05-05 15:55 ` David Sterba
2022-05-06 17:18 ` Darrick J. Wong
2022-05-07 5:26 ` Christoph Hellwig
2022-05-09 18:46 ` David Sterba
2022-05-10 3:33 ` Darrick J. Wong [this message]
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=20220510033305.GB27137@magnolia \
--to=djwong@kernel.org \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=hch@lst.de \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
/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).