From: Matthew Wilcox <willy@infradead.org>
To: "Christoph Lameter (Ampere)" <cl@linux.com>
Cc: David Rientjes <rientjes@google.com>,
Pasha Tatashin <tatashin@google.com>,
Sourav Panda <souravpanda@google.com>,
lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, linux-block@vger.kernel.org,
linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-nvme@lists.infradead.org, bpf@vger.kernel.org
Subject: Re: [LSF/MM/BPF TOPIC] State Of The Page
Date: Wed, 24 Jan 2024 17:55:46 +0000 [thread overview]
Message-ID: <ZbFPIidl6dK5cR0W@casper.infradead.org> (raw)
In-Reply-To: <aa94b8fe-fc08-2838-50b5-d1c98058b1e0@linux.com>
On Wed, Jan 24, 2024 at 09:51:02AM -0800, Christoph Lameter (Ampere) wrote:
> Can we come up with a design that uses a huge page (or some arbitrary page
> size) and the breaks out portions of the large page? That way potentially
> TLB use can be reduced (multiple sections of a large page use the same TLB)
> and defragmentation occurs because allocs and frees focus on a selection of
> large memory sections.
Could I trouble you to reply in this thread:
https://lore.kernel.org/linux-mm/Za6RXtSE_TSdrRm_@casper.infradead.org/
where I actually outline what I think we should do next.
next prev parent reply other threads:[~2024-01-24 17:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 16:24 [LSF/MM/BPF TOPIC] State Of The Page Matthew Wilcox
2024-01-19 20:31 ` Keith Busch
2024-01-20 14:11 ` Chuck Lever III
2024-01-21 21:00 ` David Rientjes
2024-01-21 23:14 ` Matthew Wilcox
2024-01-21 23:31 ` Pasha Tatashin
2024-01-21 23:54 ` Matthew Wilcox
2024-01-22 0:18 ` Pasha Tatashin
2024-01-24 17:51 ` Christoph Lameter (Ampere)
2024-01-24 17:55 ` Matthew Wilcox [this message]
2024-01-24 19:05 ` Christoph Lameter (Ampere)
2024-01-27 10:10 ` Amir Goldstein
2024-01-27 16:18 ` Matthew Wilcox
2024-01-27 17:57 ` Kent Overstreet
2024-01-27 18:43 ` Matthew Wilcox
-- strict thread matches above, loose matches on Subject: below --
2023-01-26 16:40 Matthew Wilcox
2023-02-21 16:57 ` David Howells
2023-02-21 18:08 ` Gao Xiang
2023-02-21 19:09 ` Yang Shi
2023-02-22 2:40 ` Gao Xiang
2023-02-21 19:58 ` Matthew Wilcox
2023-02-22 2:38 ` Gao Xiang
2023-03-02 3:17 ` David Rientjes
2023-03-02 3:50 ` Pasha Tatashin
2023-03-02 4:03 ` Matthew Wilcox
2023-03-02 4:16 ` Pasha Tatashin
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=ZbFPIidl6dK5cR0W@casper.infradead.org \
--to=willy@infradead.org \
--cc=bpf@vger.kernel.org \
--cc=cl@linux.com \
--cc=linux-block@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=rientjes@google.com \
--cc=souravpanda@google.com \
--cc=tatashin@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.