linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Gabriel Krisman Bertazi <krisman@suse.de>,
	 Harry Yoo <harry.yoo@oracle.com>,
	linux-mm@kvack.org, lsf-pc@lists.linux-foundation.org,
	 Mateusz Guzik <mjguzik@gmail.com>, Tejun Heo <tj@kernel.org>,
	Christoph Lameter <cl@gentwo.org>,
	 Dennis Zhou <dennis@kernel.org>,
	Vlastimil Babka <vbabka@suse.cz>, Hao Li <hao.li@linux.dev>,
	 Jan Kara <jack@suse.cz>
Subject: Re: [LSF/MM/BPF TOPIC] Ways to mitigate limitations of percpu memory allocator
Date: Thu, 5 Mar 2026 11:05:46 +0100	[thread overview]
Message-ID: <isg43f5f6igr4kcj36rr7yij4mbvrmd3plqeewkuers4ne6j7l@7vrdjl2gk5q3> (raw)
In-Reply-To: <dfbc98bd-8f80-4f7b-8209-cd5cd82bd3f0@efficios.com>

On Wed 04-03-26 23:24:37, Mathieu Desnoyers wrote:
> On 2026-03-04 12:50, Gabriel Krisman Bertazi wrote:
> > Harry Yoo <harry.yoo@oracle.com> writes:
> > 
> > > Hi folks, I'd like to discuss ways to mitigate limitations of
> > > percpu memory allocator.
> > > 
> > > While the percpu memory allocator has served its role well,
> > > it has a few problems: 1) its global lock contention, and
> > > 2) lack of features to avoid high initialization cost of percpu
> > > memory.
> > 
> > I won't be going to LSF this year.  But Jan was the proponent of my
> > dual-mode pcpu initialization work and he'll be around. I'm not sure
> > this requires a full session either, as it might not grasp broader
> > interest.  Are Mathieu and Mateusz attending?
> 
> No sorry, I was not planning to attend in person this year.
> Is it possible to attend remotely ?

We don't offer general remote attendance option but we will have two
meeting owls available on site so we can set up something on case-by-case
basis. If you're interested in remotely participating in this session,
please talk to MM track leaders how / whether they can accommodate this.

								Honza
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR


  reply	other threads:[~2026-03-05 10:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27  6:41 Harry Yoo
2026-03-04 17:50 ` Gabriel Krisman Bertazi
2026-03-05  4:24   ` Mathieu Desnoyers
2026-03-05 10:05     ` Jan Kara [this message]
2026-03-05 11:33 ` Pedro Falcato
2026-03-05 11:48   ` Jan Kara

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=isg43f5f6igr4kcj36rr7yij4mbvrmd3plqeewkuers4ne6j7l@7vrdjl2gk5q3 \
    --to=jack@suse.cz \
    --cc=cl@gentwo.org \
    --cc=dennis@kernel.org \
    --cc=hao.li@linux.dev \
    --cc=harry.yoo@oracle.com \
    --cc=krisman@suse.de \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mjguzik@gmail.com \
    --cc=tj@kernel.org \
    --cc=vbabka@suse.cz \
    /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