From: "JP Kobryn (Meta)" <jp.kobryn@linux.dev>
To: Christoph Hellwig <hch@infradead.org>
Cc: boris@bur.io, mark@harmstone.com, clm@fb.com, wqu@suse.com,
dsterba@suse.com, linux-btrfs@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-team@meta.com
Subject: Re: [PATCH 2/2] btrfs: prevent direct reclaim during compressed readahead
Date: Fri, 20 Mar 2026 09:17:55 -0700 [thread overview]
Message-ID: <a74f3ed6-0f31-40ed-aeea-436aa20cb359@linux.dev> (raw)
In-Reply-To: <abz49WgkJ-KpmBcN@infradead.org>
On 3/20/26 12:36 AM, Christoph Hellwig wrote:
> On Fri, Mar 20, 2026 at 12:34:45AM -0700, JP Kobryn (Meta) wrote:
>> Prevent direct reclaim during compressed readahead.
>
> This completely fails to explain why you want that.
I see that now.
Qu also had a good point about including info on why the current flags
are an issue. Some of the cover letter text would help here. I'll bring
some of that over and expand on it so we have the relevant details here.
next prev parent reply other threads:[~2026-03-20 16:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 7:34 [PATCH 0/2] btrfs: prevent direct reclaim during compressed readahead JP Kobryn (Meta)
2026-03-20 7:34 ` [PATCH 1/2] btrfs: additional gfp api for allocating compressed folios JP Kobryn (Meta)
2026-03-20 11:11 ` Mark Harmstone
2026-03-20 17:55 ` David Sterba
2026-03-20 7:34 ` [PATCH 2/2] btrfs: prevent direct reclaim during compressed readahead JP Kobryn (Meta)
2026-03-20 7:36 ` Christoph Hellwig
2026-03-20 16:17 ` JP Kobryn (Meta) [this message]
2026-03-20 10:12 ` Qu Wenruo
2026-03-20 11:14 ` Mark Harmstone
2026-03-20 11:11 ` Mark Harmstone
2026-03-20 11:10 ` [PATCH 0/2] " Mark Harmstone
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=a74f3ed6-0f31-40ed-aeea-436aa20cb359@linux.dev \
--to=jp.kobryn@linux.dev \
--cc=boris@bur.io \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=hch@infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-team@meta.com \
--cc=mark@harmstone.com \
--cc=wqu@suse.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