From: Christoph Hellwig <hch@infradead.org>
To: dsterba@suse.cz, Johannes Thumshirn <Johannes.Thumshirn@wdc.com>,
David Sterba <dsterba@suse.com>,
Nikolay Borisov <nborisov@suse.com>,
"linux-btrfs @ vger . kernel . org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v3 0/5] btrfs: remove buffer heads form superblock handling
Date: Thu, 30 Jan 2020 05:39:21 -0800 [thread overview]
Message-ID: <20200130133921.GA21841@infradead.org> (raw)
In-Reply-To: <20200130121530.GO3929@twin.jikos.cz>
On Thu, Jan 30, 2020 at 01:15:30PM +0100, David Sterba wrote:
> > Sure but with hch's proposed change to using read_cache_page_gfp() this
> > doesn't make too much sense anymore at least for the read path.
> >
> > Maybe "use page cache for superblock reading"?
>
> That works too. We might need a new iteration that summarizes up all the
> feedback so far, so we have same code to refer to.
Per my question on the second patch: why even use the page cache at
all. btrfs already caches the value outside the pagecache, so why
even bother with the page cache overhead?
next prev parent reply other threads:[~2020-01-30 13:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 15:59 [PATCH v3 0/5] btrfs: remove buffer heads form superblock handling Johannes Thumshirn
2020-01-27 15:59 ` [PATCH v3 1/5] btrfs: remove buffer heads from super block reading Johannes Thumshirn
2020-01-28 11:47 ` Christoph Hellwig
2020-01-30 10:12 ` Johannes Thumshirn
2020-01-27 15:59 ` [PATCH v3 2/5] btrfs: remove use of buffer_heads from superblock writeout Johannes Thumshirn
2020-01-28 11:52 ` Christoph Hellwig
2020-01-27 15:59 ` [PATCH v3 3/5] btrfs: remove btrfsic_submit_bh() Johannes Thumshirn
2020-01-27 15:59 ` [PATCH v3 4/5] btrfs: remove buffer_heads from btrfsic_process_written_block() Johannes Thumshirn
2020-01-27 15:59 ` [PATCH v3 5/5] btrfs: remove buffer_heads form superblock mirror integrity checking Johannes Thumshirn
2020-01-29 14:25 ` [PATCH v3 0/5] btrfs: remove buffer heads form superblock handling David Sterba
2020-01-30 11:23 ` Johannes Thumshirn
2020-01-30 12:15 ` David Sterba
2020-01-30 13:39 ` Christoph Hellwig [this message]
2020-01-30 15:53 ` Johannes Thumshirn
2020-01-30 15:56 ` Christoph Hellwig
2020-01-30 16:09 ` Johannes Thumshirn
2020-01-30 16:15 ` Christoph Hellwig
2020-01-30 16:16 ` David Sterba
2020-01-31 13:43 ` Johannes Thumshirn
2020-02-03 8:29 ` Christoph Hellwig
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=20200130133921.GA21841@infradead.org \
--to=hch@infradead.org \
--cc=Johannes.Thumshirn@wdc.com \
--cc=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@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