linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: "Liao, Chang" <liaochang1@huawei.com>
Cc: andrii@kernel.org, linux-kernel@vger.kernel.org,
	 linux-trace-kernel@vger.kernel.org,
	linux-perf-users@vger.kernel.org,  bpf@vger.kernel.org,
	Mark Rutland <mark.rutland@arm.com>,
	 Peter Zijlstra <peterz@infradead.org>,
	Oleg Nesterov <oleg@redhat.com>,
	 Masami Hiramatsu <mhiramat@kernel.org>
Subject: Re: [PATCH v2] uprobes: Improve the usage of xol slots for better scalability
Date: Wed, 6 Nov 2024 08:27:19 -0800	[thread overview]
Message-ID: <CAEf4BzbJZ72Yr6tQuGLpz6fpKFXeUw3cD1BRO3T3j1psV4Qkdg@mail.gmail.com> (raw)
In-Reply-To: <8bcc6d5b-08d6-48a8-99d2-d8bb2bef2d6c@huawei.com>

On Wed, Nov 6, 2024 at 1:12 AM Liao, Chang <liaochang1@huawei.com> wrote:
>
>
>
> 在 2024/9/27 17:45, Liao Chang 写道:
> >>  2 files changed, 139 insertions(+), 42 deletions(-)
> >>
> > Liao,
> >
> > Assuming your ARM64 improvements go through, would you still need
> > these changes? XOL case is a slow case and if possible should be
> > avoided at all costs. If all common cases for ARM64 are covered
> > through instruction emulation, would we need to add all this
> > complexity to optimize slow case?
>
> Andrii,
>
> I've studied the optimizations merged over the past month, it seems
> that part of the problem addressed in this patch has been resolved
> by Oleg(uprobes: kill xol_area->slot_count). And I hope you've received
> the email with the re-run results for -push using simulated STP on
> the latest kernel (tag next-20241104). It show significant improvements,
> althought there's still room to match the throughput of -nop and -ret.
> So based on these results, I would prioritize the STP simulation patch.

Great, I was hoping that Oleg's patches would help. And yes, I
absolutely agree, STP simulation to avoid kernel->user->kernel switch
is probably the biggest bang for the buck for ARM64 specifically now.
Can you please send a fastest simulation approach that works like
x86-64, and we can try to continue conversation on the refreshed
patch?

>
> --
> BR
> Liao, Chang
>

      reply	other threads:[~2024-11-06 16:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-27  9:45 [PATCH v2] uprobes: Improve the usage of xol slots for better scalability Liao Chang
2024-09-27 17:18 ` Oleg Nesterov
2024-10-21 12:03   ` Liao, Chang
2024-09-30 21:04 ` Andrii Nakryiko
2024-10-01 14:29 ` Oleg Nesterov
2024-10-21 12:08   ` Liao, Chang
2024-11-06  9:12 ` Liao, Chang
2024-11-06 16:27   ` Andrii Nakryiko [this message]

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=CAEf4BzbJZ72Yr6tQuGLpz6fpKFXeUw3cD1BRO3T3j1psV4Qkdg@mail.gmail.com \
    --to=andrii.nakryiko@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=liaochang1@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mhiramat@kernel.org \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).