linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: "Liao, Chang" <liaochang1@huawei.com>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	 linux-kernel@vger.kernel.org,
	linux-trace-kernel@vger.kernel.org,
	 linux-perf-users@vger.kernel.org, bpf@vger.kernel.org,
	 Andrii Nakryiko <andrii@kernel.org>,
	Oleg Nesterov <oleg@redhat.com>
Subject: Re: [PATCH v3 0/2] uprobes: Improve scalability by reducing the contention on siglock
Date: Mon, 21 Oct 2024 10:18:11 -0700	[thread overview]
Message-ID: <CAEf4BzYUdPJrgy1Dqinxk5ATPxA8WCTzQW3QcWobZpXjiYDZNw@mail.gmail.com> (raw)
In-Reply-To: <e62dbebc-d366-453a-b305-67f50baeff05@huawei.com>

On Mon, Oct 21, 2024 at 3:43 AM Liao, Chang <liaochang1@huawei.com> wrote:
>
>
>
> 在 2024/10/12 3:34, Andrii Nakryiko 写道:
> > On Tue, Sep 17, 2024 at 7:05 PM Liao, Chang <liaochang1@huawei.com> wrote:
> >>
> >> Hi, Peter and Masami
> >>
> >> I look forward to your inputs on these series. Andrii has proven they are
> >> hepful for uprobe scalability.
> >>
> >> Thanks.
> >>
> >> 在 2024/9/15 23:18, Oleg Nesterov 写道:
> >>> Hi Liao,
> >>>
> >>> On 09/14, Liao, Chang wrote:
> >>>>
> >>>> Hi, Oleg
> >>>>
> >>>> Kindly ping.
> >>>>
> >>>> This series have been pending for a month. Is thre any issue I overlook?
> >>>
> >>> Well, I have already acked both patches.
> >>>
> >>> Please resend them to Peter/Masami, with my acks included.
> >>>
> >
> > Hey Liao,
> >
> > I didn't see v4 from you for this patch set with Oleg's acks. Did you
> > get a chance to rebase, add acks, and send the latest version?
>
> Andrii,
>
> I am ready to send v4 based on the latest kernel from next tree. Otherwise,
> I haven't heard back from any of maintainers except Oleg, so I'm a bit unsure
> if I should make further changes to this series.
>

Let's just rebase to the latest tip/perf/core and resend with Oleg's
ack. Hopefully this should be enough.

> >
> >>> Oleg.
> >>>
> >>>
> >>
> >> --
> >> BR
> >> Liao, Chang
>
> --
> BR
> Liao, Chang
>

  reply	other threads:[~2024-10-21 17:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-15  1:46 [PATCH v3 0/2] uprobes: Improve scalability by reducing the contention on siglock Liao Chang
2024-08-15  1:46 ` [PATCH v3 1/2] uprobes: Remove redundant spinlock in uprobe_deny_signal() Liao Chang
2024-10-22  4:01   ` Masami Hiramatsu
2024-08-15  1:46 ` [PATCH v3 2/2] uprobes: Remove the spinlock within handle_singlestep() Liao Chang
2024-10-22  4:01   ` Masami Hiramatsu
2024-09-14  2:53 ` [PATCH v3 0/2] uprobes: Improve scalability by reducing the contention on siglock Liao, Chang
2024-09-15 15:18   ` Oleg Nesterov
2024-09-18  2:05     ` Liao, Chang
2024-10-11 19:34       ` Andrii Nakryiko
2024-10-21 10:43         ` Liao, Chang
2024-10-21 17:18           ` Andrii Nakryiko [this message]
2024-10-22  6:18             ` Liao, Chang

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=CAEf4BzYUdPJrgy1Dqinxk5ATPxA8WCTzQW3QcWobZpXjiYDZNw@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=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).