[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56099e59-586d-4013-8262-a21a3ae473a4@huawei.com>
Date: Mon, 21 Oct 2024 20:08:59 +0800
From: "Liao, Chang" <liaochang1@...wei.com>
To: Oleg Nesterov <oleg@...hat.com>
CC: <ak@...ux.intel.com>, <mhiramat@...nel.org>, <andrii@...nel.org>,
<peterz@...radead.org>, <mingo@...hat.com>, <acme@...nel.org>,
<namhyung@...nel.org>, <mark.rutland@....com>,
<alexander.shishkin@...ux.intel.com>, <jolsa@...nel.org>,
<irogers@...gle.com>, <adrian.hunter@...el.com>, <kan.liang@...ux.intel.com>,
<linux-kernel@...r.kernel.org>, <linux-trace-kernel@...r.kernel.org>,
<linux-perf-users@...r.kernel.org>, <bpf@...r.kernel.org>
Subject: Re: [PATCH v2] uprobes: Improve the usage of xol slots for better
scalability
在 2024/10/1 22:29, Oleg Nesterov 写道:
> On 09/27, Liao Chang wrote:
>>
>> The uprobe handler allocates xol slot from xol_area and quickly release
>> it in the single-step handler. The atomic operations on the xol bitmap
>> and slot_count lead to expensive cache line bouncing between multiple
>> CPUs.
>
> Liao, could you please check if this series
>
> [PATCH 0/2] uprobes: kill xol_area->slot_count
> https://lore.kernel.org/all/20241001142416.GA13599@redhat.com/
>
> makes any difference performance-wise in your testing?
OK, I am ready to test this patch on my arm64 machine.
>
> Oleg.
>
>
--
BR
Liao, Chang
Powered by blists - more mailing lists