From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: "wuqiang.matt" <wuqiang.matt@bytedance.com>
Cc: linux-trace-kernel@vger.kernel.org, davem@davemloft.net,
anil.s.keshavamurthy@intel.com, naveen.n.rao@linux.ibm.com,
rostedt@goodmis.org, peterz@infradead.org,
akpm@linux-foundation.org, sander@svanheule.net,
ebiggers@google.com, dan.j.williams@intel.com,
jpoimboe@kernel.org, linux-kernel@vger.kernel.org, lkp@intel.com,
mattwu@163.com
Subject: Re: [PATCH v11 0/5] lib,kprobes: kretprobe scalability improvement
Date: Thu, 19 Oct 2023 00:13:03 +0900 [thread overview]
Message-ID: <20231019001303.befd514dd103d334527e1754@kernel.org> (raw)
In-Reply-To: <20231017135654.82270-1-wuqiang.matt@bytedance.com>
Hi,
On Tue, 17 Oct 2023 21:56:49 +0800
"wuqiang.matt" <wuqiang.matt@bytedance.com> wrote:
> This patch series introduces a scalable and lockless ring-array based
> object pool to improve scalability of kretprobed routines.
>
> v11:
> *) patchset rebased to branch probes/core of linux-trace.git
> *) objpool: objpool_fini optimized for better code readability
> *) test_objpool: asynchronous releasing of objpool now covered
>
> wuqiang.matt (5):
> lib: objpool added: ring-array based lockless MPMC
> lib: objpool test module added
> kprobes: kretprobe scalability improvement with objpool
> kprobes: freelist.h removed
> MAINTAINERS: objpool added
OK, this version looks good to me.
Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
I'll pick this series on for-next branch.
Thank you,
>
> MAINTAINERS | 7 +
> include/linux/freelist.h | 129 --------
> include/linux/kprobes.h | 11 +-
> include/linux/objpool.h | 176 ++++++++++
> include/linux/rethook.h | 16 +-
> kernel/kprobes.c | 93 +++---
> kernel/trace/fprobe.c | 32 +-
> kernel/trace/rethook.c | 90 +++--
> lib/Kconfig.debug | 11 +
> lib/Makefile | 4 +-
> lib/objpool.c | 286 ++++++++++++++++
> lib/test_objpool.c | 689 +++++++++++++++++++++++++++++++++++++++
> 12 files changed, 1270 insertions(+), 274 deletions(-)
> delete mode 100644 include/linux/freelist.h
> create mode 100644 include/linux/objpool.h
> create mode 100644 lib/objpool.c
> create mode 100644 lib/test_objpool.c
>
> --
> 2.40.1
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
prev parent reply other threads:[~2023-10-18 15:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 13:56 [PATCH v11 0/5] lib,kprobes: kretprobe scalability improvement wuqiang.matt
2023-10-17 13:56 ` [PATCH v11 1/5] lib: objpool added: ring-array based lockless MPMC wuqiang.matt
2023-10-18 2:18 ` Chengming Zhou
2023-10-18 4:08 ` wuqiang.matt
2023-10-17 13:56 ` [PATCH v11 2/5] lib: objpool test module added wuqiang.matt
2023-10-17 13:56 ` [PATCH v11 3/5] kprobes: kretprobe scalability improvement wuqiang.matt
2023-10-17 13:56 ` [PATCH v11 4/5] kprobes: freelist.h removed wuqiang.matt
2023-10-17 13:56 ` [PATCH v11 5/5] MAINTAINERS: objpool added wuqiang.matt
2023-10-18 15:13 ` Masami Hiramatsu [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=20231019001303.befd514dd103d334527e1754@kernel.org \
--to=mhiramat@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=dan.j.williams@intel.com \
--cc=davem@davemloft.net \
--cc=ebiggers@google.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mattwu@163.com \
--cc=naveen.n.rao@linux.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sander@svanheule.net \
--cc=wuqiang.matt@bytedance.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.