[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220607153544.7727e87f669ea3a7c9f4a6b5@linux-foundation.org>
Date: Tue, 7 Jun 2022 15:35:44 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: "Uladzislau Rezki (Sony)" <urezki@...il.com>
Cc: linux-mm@...ck.org, LKML <linux-kernel@...r.kernel.org>,
Christoph Hellwig <hch@...radead.org>,
Matthew Wilcox <willy@...radead.org>,
Nicholas Piggin <npiggin@...il.com>,
Oleksiy Avramchenko <oleksiy.avramchenko@...y.com>
Subject: Re: [PATCH 0/5] Reduce a vmalloc internal lock contention
preparation work
On Tue, 7 Jun 2022 11:34:44 +0200 "Uladzislau Rezki (Sony)" <urezki@...il.com> wrote:
> This small serias is a preparation work to implement per-cpu vmalloc
> allocation in order to reduce a high internal lock contention. This
> series does not introduce any functional changes, it is only about
> preparation.
I can toss it in for some runtime testing, but...
What lock are we talking about here, what is the magnitude of the
performance issues it is causing and what is the status of the patch
which uses all this preparation?
Powered by blists - more mailing lists