From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: Luis Henriques <lhenriques@suse.de>
Cc: Jan Kara <jack@suse.cz>, Matthew Wilcox <willy@infradead.org>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [Lsf-pc] [LSF/MM/BPF TOPIC] Removing GFP_NOFS
Date: Tue, 9 Jan 2024 18:04:12 +0000 [thread overview]
Message-ID: <274c4bce-1104-4126-8a85-65a603a2980a@wdc.com> (raw)
In-Reply-To: <87cyua33vv.fsf@suse.de>
On 09.01.24 16:47, Luis Henriques wrote:
> Johannes Thumshirn <Johannes.Thumshirn@wdc.com> writes:
>>
>> As I've already feared we (as in btrfs) are the worst here.
>
> It probably won't make you feel any better, but the value for ceph isn't
> correct as you're just taking into account the code in 'fs/ceph/'. If you
> also take 'net/ceph/', it brings it much closer to btrfs: 63 + 48 = 111
>
> Cheers,
Yeah I've just quickly skimmed over fs/. There's net/ (69) and drivers/
(36) as well.
next prev parent reply other threads:[~2024-01-09 18:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 21:17 Matthew Wilcox
2024-01-05 10:13 ` Viacheslav Dubeyko
2024-01-05 10:26 ` [Lsf-pc] " Jan Kara
2024-01-05 14:17 ` Viacheslav Dubeyko
2024-01-05 14:35 ` Vlastimil Babka (SUSE)
2024-01-05 10:57 ` [Lsf-pc] " Jan Kara
2024-01-08 11:47 ` Johannes Thumshirn
2024-01-08 17:39 ` David Sterba
2024-01-09 7:43 ` Johannes Thumshirn
2024-01-09 22:23 ` Dave Chinner
2024-01-09 15:47 ` Luis Henriques
2024-01-09 18:04 ` Johannes Thumshirn [this message]
2024-01-08 6:39 ` Dave Chinner
2024-01-09 4:47 ` Dave Chinner
2024-02-08 16:02 ` Vlastimil Babka (SUSE)
2024-02-08 17:33 ` Michal Hocko
2024-02-08 19:55 ` Vlastimil Babka (SUSE)
2024-02-08 22:45 ` Kent Overstreet
2024-02-12 1:20 ` Dave Chinner
2024-02-12 2:06 ` Kent Overstreet
2024-02-12 4:35 ` Dave Chinner
2024-02-12 19:30 ` Kent Overstreet
2024-02-12 22:07 ` Dave Chinner
2024-01-09 22:44 ` Dave Chinner
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=274c4bce-1104-4126-8a85-65a603a2980a@wdc.com \
--to=johannes.thumshirn@wdc.com \
--cc=jack@suse.cz \
--cc=lhenriques@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=willy@infradead.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