From: Uladzislau Rezki <urezki@gmail.com>
To: Michal Hocko <mhocko@suse.com>
Cc: Uladzislau Rezki <urezki@gmail.com>,
lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org
Subject: Re: [Lsf-pc] LSFMMBPF proposal [MM]: Eliminate vmap/vmalloc lock contention
Date: Mon, 24 Apr 2023 09:44:00 +0200 [thread overview]
Message-ID: <ZEYzQBBCByYMEpjB@pc636> (raw)
In-Reply-To: <ZEJ7n7f7UO4JrfDh@dhcp22.suse.cz>
On Fri, Apr 21, 2023 at 02:03:43PM +0200, Michal Hocko wrote:
> On Tue 28-02-23 17:42:43, Uladzislau Rezki wrote:
> > Hello, LSF.
> >
> > Title: Introduce a per-cpu-vmap-cache to eliminate a vmap lock contention
> >
> > Description:
> > Currently the vmap code is not scaled to number of CPU cores in a system
> > because a global vmap space is protected by a single spinlock. Such approach
> > has a clear bottleneck if many CPUs simultaneously access to one resource.
> >
> > In this talk i would like to describe a drawback, show some data related
> > to contentions and places where those occur in a code. Apart of that i
> > would like to share ideas how to eliminate it providing a few approaches
> > and compare them.
>
> It's been some time since you brough this up. Has there been any
> progress on the topic? Do you still find it important to discuss it at
> LSFMM?
>
The idea about sequence was/is:
1) Give an overview on the proposal;
2) Submit patches to address the problem;
3) Start a discussion over lkml with people who are interested in it;
4) Send out a complete solution.
--
Uladzislau Rezki
next prev parent reply other threads:[~2023-04-24 7:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 16:42 LSFMMBPF proposal [MM]: Eliminate vmap/vmalloc lock contention Uladzislau Rezki
2023-03-21 7:48 ` Lorenzo Stoakes
2023-04-21 12:03 ` [Lsf-pc] " Michal Hocko
2023-04-24 7:44 ` Uladzislau Rezki [this message]
2023-04-24 8:55 ` Michal Hocko
2023-04-24 10:08 ` Uladzislau Rezki
2023-04-24 10:22 ` Lorenzo Stoakes
2023-04-25 1:11 ` Baoquan He
2023-05-11 16:46 ` Uladzislau Rezki
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=ZEYzQBBCByYMEpjB@pc636 \
--to=urezki@gmail.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mhocko@suse.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.