From: Andreas Dilger <adilger@dilger.ca>
To: Matthew Wilcox <willy@infradead.org>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: Discontiguous folios/pagesets
Date: Sat, 28 Aug 2021 13:27:29 -0600 [thread overview]
Message-ID: <1FC3646C-259F-4AA4-B7E0-B13E19EDC595@dilger.ca> (raw)
In-Reply-To: <YSqIry5dKg+kqAxJ@casper.infradead.org>
[-- Attachment #1: Type: text/plain, Size: 807 bytes --]
On Aug 28, 2021, at 1:04 PM, Matthew Wilcox <willy@infradead.org> wrote:
>
> The current folio work is focused on permitting the VM to use
> physically contiguous chunks of memory. Both Darrick and Johannes
> have pointed out the advantages of supporting logically-contiguous,
> physically-discontiguous chunks of memory. Johannes wants to be able to
> use order-0 allocations to allocate larger folios, getting the benefit
> of managing the memory in larger chunks without requiring the memory
> allocator to be able to find contiguous chunks. Darrick wants to support
> non-power-of-two block sizes.
What is the use case for non-power-of-two block sizes? The main question
is whether that use case is important enough to add the complexity and
overhead in order to support it?
Cheers, Andreas
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 873 bytes --]
next prev parent reply other threads:[~2021-08-28 19:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-28 19:04 Discontiguous folios/pagesets Matthew Wilcox
2021-08-28 19:27 ` Andreas Dilger [this message]
2021-08-30 18:28 ` Darrick J. Wong
2021-08-30 18:35 ` Andreas Dilger
2021-08-30 18:43 ` Matthew Wilcox
2021-09-01 9:40 ` 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=1FC3646C-259F-4AA4-B7E0-B13E19EDC595@dilger.ca \
--to=adilger@dilger.ca \
--cc=darrick.wong@oracle.com \
--cc=hannes@cmpxchg.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).