All of lore.kernel.org
 help / color / mirror / Atom feed
From: Usama Arif <usama.arif@linux.dev>
To: Kiryl Shutsemau <kas@kernel.org>,
	Ryan Roberts <ryan.roberts@arm.com>,
	Matthew Wilcox <willy@infradead.org>
Cc: linux-mm@kvack.org, lsf-pc@lists.linux-foundation.org
Subject: Re: Large memory allocations at LSF/MM
Date: Mon, 27 Apr 2026 12:45:39 +0100	[thread overview]
Message-ID: <9cecea5d-9377-4d90-97c3-0cd8b2f77b35@linux.dev> (raw)
In-Reply-To: <ae9AHWvXUTuoqlfA@thinkstation>



On 27/04/2026 11:58, Kiryl Shutsemau wrote:
> On Mon, Apr 27, 2026 at 11:46:51AM +0100, Ryan Roberts wrote:
>> On 23/04/2026 16:52, Matthew Wilcox wrote:
>>> We've had far too many proposals for the MM track this year.  In an
>>> effort to squeeze in as many topics as possible, I've currently
>>> scheduled your three talks into a 1 hour timeslot.  I think there's a
>>> fair amount of overlap between the topics and we probably can get a
>>> decent amount of conversation going here.
>>>
>>> If you feel you need the full half hour each, let me know and I'll
>>> try to come up with some other way to squeeze something in.
>>>
>>
>> Thanks for squeezing this in and sorry for the slow response. Yes I can make it
>> work in 20 mins.
> 
> +1. We can continue discussion outside of the session if needed.
> 

Good for me as well. Thanks for organizing!



  reply	other threads:[~2026-04-27 11:45 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 [this message]
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
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=9cecea5d-9377-4d90-97c3-0cd8b2f77b35@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=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.