Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: Christoph Hellwig <hch@lst.de>, Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: clm@fb.com, dsterba@suse.com, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2] btrfs: don't limit direct reads to a single sector
Date: Tue, 21 Jun 2022 14:55:06 +0800	[thread overview]
Message-ID: <2bb7e620-fb2c-52d3-0ecf-87c2f75a1305@suse.com> (raw)
In-Reply-To: <20220621064010.GA893@lst.de>



On 2022/6/21 14:40, Christoph Hellwig wrote:
> On Tue, Jun 21, 2022 at 02:35:55PM +0800, Qu Wenruo wrote:
>> In fact, one bio vector can point to multiple pages, as its bv_len can
>> be larger than PAGE_SIZE.
> 
> Yes, it can.  But it usually doesn't, as that requires contigous memory.

That's true.

> Without the large folio support now merges for xfs/iomap that is very
> unusual and tends to happen only soon after booting.

A little off-topic here, what did the extra XFS/iomap do here?

IIRC the multi-page bio vector is already there for years.

As long as the pages in page cache are contiguous, bio_add_page() will 
create such multi-page vector, without any extra support from fs.

>  At which point
> allocating the larger csums array is also not a problem as we can
> find contigous memory for that easily as well.  For direct I/O on the
> other hand the destination could be THPs or hugetlbs even when memory
> is badly fragmented.

My point here is just no need to align any limit.

Smash a good enough value here is enough, or we need to dig way deeper 
to see if the MAX_SECTORS based one is really correct or not.

Thanks,
Qu

  reply	other threads:[~2022-06-21  6:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-21  6:26 [PATCH v2] btrfs: don't limit direct reads to a single sector Christoph Hellwig
2022-06-21  6:35 ` Qu Wenruo
2022-06-21  6:40   ` Christoph Hellwig
2022-06-21  6:55     ` Qu Wenruo [this message]
2022-06-21  6:59       ` Christoph Hellwig
2022-06-21  7:04         ` Qu Wenruo
2022-06-21  8:37 ` Nikolay Borisov
2022-06-21 13:34 ` David Sterba

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=2bb7e620-fb2c-52d3-0ecf-87c2f75a1305@suse.com \
    --to=wqu@suse.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=hch@lst.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.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