From: Usama Arif <usama.arif@linux.dev>
To: Matthew Wilcox <willy@infradead.org>, Vlastimil Babka <vbabka@suse.com>
Cc: Kiryl Shutsemau <kas@kernel.org>,
Ryan Roberts <ryan.roberts@arm.com>,
linux-mm@kvack.org, lsf-pc@lists.linux-foundation.org
Subject: Re: [Lsf-pc] Large memory allocations at LSF/MM
Date: Tue, 28 Apr 2026 15:07:43 +0100 [thread overview]
Message-ID: <ecf66354-6ec4-42c7-9f08-a95f403b55a0@linux.dev> (raw)
In-Reply-To: <ae9heafyGwN3ctUe@casper.infradead.org>
On 27/04/2026 14:15, Matthew Wilcox wrote:
> On Mon, Apr 27, 2026 at 02:35:45PM +0200, Vlastimil Babka wrote:
>> Well meanwhile we managed to extend the session to 1:30 :)
>>
>> ICYMI:
>> https://docs.google.com/spreadsheets/d/1mGEdDrWskp7Ua91jGXzquQGinorcD58DAVXhOiRp2Gg/edit?usp=sharing
>
> Sorry, I meant to follow up with the good news that we found some more
> time. If you guys want, I can split you apart into three separate
> topics, or just leave it as a Hydra session. It all feels pretty
> connected to me, so maybe keep it all the way it is?
For the 1G THP, I think might be good to keep it separate? I feel
like there were many different paths proposed on how we can go forward
and that work isn't applicable to the other proposals? That said, I am
flexible either way, happy to go with whatever works best for the group!
>
> Looking forward to seeing you all next week!
next prev parent reply other threads:[~2026-04-28 14:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 15:52 Large memory allocations at LSF/MM Matthew Wilcox
2026-04-27 10:46 ` Ryan Roberts
2026-04-27 10:58 ` Kiryl Shutsemau
2026-04-27 11:45 ` Usama Arif
2026-04-27 12:35 ` [Lsf-pc] " Vlastimil Babka
2026-04-27 13:15 ` Matthew Wilcox
2026-04-28 11:26 ` Ryan Roberts
2026-04-28 14:07 ` Usama Arif [this message]
2026-04-28 14:28 ` Matthew Wilcox
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=ecf66354-6ec4-42c7-9f08-a95f403b55a0@linux.dev \
--to=usama.arif@linux.dev \
--cc=kas@kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=ryan.roberts@arm.com \
--cc=vbabka@suse.com \
--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 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.