Large memory allocations at LSF/MM

Large memory allocations at LSF/MM

[Matthew Wilcox]

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.

Re: Large memory allocations at LSF/MM

[Ryan Roberts]

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.

Thanks,
Ryan

Re: Large memory allocations at LSF/MM

[Kiryl Shutsemau]

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.

-- 
  Kiryl Shutsemau / Kirill A. Shutemov

Re: Large memory allocations at LSF/MM

[Usama Arif]

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!

Re: [Lsf-pc] Large memory allocations at LSF/MM

[Vlastimil Babka]

On 4/27/26 13:45, Usama Arif wrote:
> 
> 
> 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!

Well meanwhile we managed to extend the session to 1:30 :)

ICYMI:
https://docs.google.com/spreadsheets/d/1mGEdDrWskp7Ua91jGXzquQGinorcD58DAVXhOiRp2Gg/edit?usp=sharing

> _______________________________________________
> Lsf-pc mailing list
> Lsf-pc@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/lsf-pc

Re: [Lsf-pc] Large memory allocations at LSF/MM

[Matthew Wilcox]

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?

Looking forward to seeing you all next week!

Re: [Lsf-pc] Large memory allocations at LSF/MM

[Ryan Roberts]

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?

I'm easy; I'll have a few slides to present that are specific to my topic, but
happy do it as a combined session...

> 
> Looking forward to seeing you all next week!

Absolutely, looking forward to it!

Re: [Lsf-pc] Large memory allocations at LSF/MM

[Usama Arif]

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!

Re: [Lsf-pc] Large memory allocations at LSF/MM

[Matthew Wilcox]

On Tue, Apr 28, 2026 at 03:07:43PM +0100, Usama Arif wrote:
> 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!

I can split yours off into its own session and keep the other two
together for now.  I feel yours fits better after the other two, so
I'll give you 12:30-13:00 and leave the other two in 11:30 to 12:30 for
now.