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 v10 1/5] lib: objpool added: ring-array based lockless MPMC
Date: Mon, 16 Oct 2023 08:26:59 +0900 [thread overview]
Message-ID: <20231016082659.6ca94a5dff368783698753f9@kernel.org> (raw)
In-Reply-To: <1516f7d1-e11b-3244-76b9-e6ddafc29a32@bytedance.com>
On Mon, 16 Oct 2023 00:06:11 +0800
"wuqiang.matt" <wuqiang.matt@bytedance.com> wrote:
> On 2023/10/15 23:43, Masami Hiramatsu (Google) wrote:
> > On Sun, 15 Oct 2023 13:32:47 +0800
> > "wuqiang.matt" <wuqiang.matt@bytedance.com> wrote:
> >
> >> objpool is a scalable implementation of high performance queue for
> >> object allocation and reclamation, such as kretprobe instances.
> >>
> >> With leveraging percpu ring-array to mitigate hot spots of memory
> >> contention, it delivers near-linear scalability for high parallel
> >> scenarios. The objpool is best suited for the following cases:
> >> 1) Memory allocation or reclamation are prohibited or too expensive
> >> 2) Consumers are of different priorities, such as irqs and threads
> >>
> >> Limitations:
> >> 1) Maximum objects (capacity) is fixed after objpool creation
> >> 2) All pre-allocated objects are managed in percpu ring array,
> >> which consumes more memory than linked lists
> >>
> >
> > Thanks for updating! This looks good to me except 2 points.
> >
> > [...]
> >> +
> >> +/* initialize object pool and pre-allocate objects */
> >> +int objpool_init(struct objpool_head *pool, int nr_objs, int object_size,
> >> + gfp_t gfp, void *context, objpool_init_obj_cb objinit,
> >> + objpool_fini_cb release)
> >> +{
> >> + int rc, capacity, slot_size;
> >> +
> >> + /* check input parameters */
> >> + if (nr_objs <= 0 || nr_objs > OBJPOOL_NR_OBJECT_MAX ||
> >> + object_size <= 0 || object_size > OBJPOOL_OBJECT_SIZE_MAX)
> >> + return -EINVAL;
> >> +
> >> + /* align up to unsigned long size */
> >> + object_size = ALIGN(object_size, sizeof(long));
> >> +
> >> + /* calculate capacity of percpu objpool_slot */
> >> + capacity = roundup_pow_of_two(nr_objs);
> >
> > This must be 'roundup_pow_of_two(nr_objs + 1)' because if nr_objs is power
> > of 2 and all objects are pushed on the same slot, tail == head. This
> > means empty and full is the same.
>
> That won't happen. Would tail and head wrap only when >= 2^32. When all
> objects are pushed to the same slot, tail will be (head + capacity).
Ah, indeed. OK.
>
> >
> >> + if (!capacity)
> >> + return -EINVAL;
> >> +
> >> + /* initialize objpool pool */
> >> + memset(pool, 0, sizeof(struct objpool_head));
> >> + pool->nr_cpus = nr_cpu_ids;
> >> + pool->obj_size = object_size;
> >> + pool->capacity = capacity;
> >> + pool->gfp = gfp & ~__GFP_ZERO;
> >> + pool->context = context;
> >> + pool->release = release;
> >> + slot_size = pool->nr_cpus * sizeof(struct objpool_slot);
> >> + pool->cpu_slots = kzalloc(slot_size, pool->gfp);
> >> + if (!pool->cpu_slots)
> >> + return -ENOMEM;
> >> +
> >> + /* initialize per-cpu slots */
> >> + rc = objpool_init_percpu_slots(pool, nr_objs, context, objinit);
> >> + if (rc)
> >> + objpool_fini_percpu_slots(pool);
> >> + else
> >> + refcount_set(&pool->ref, pool->nr_objs + 1);
> >> +
> >> + return rc;
> >> +}
> >> +EXPORT_SYMBOL_GPL(objpool_init);
> >> +
> >
> > [...]
> >
> >> +
> >> +/* drop unused objects and defref objpool for releasing */
> >> +void objpool_fini(struct objpool_head *pool)
> >> +{
> >> + void *obj;
> >> +
> >> + do {
> >> + /* grab object from objpool and drop it */
> >> + obj = objpool_pop(pool);
> >> +
> >> + /*
> >> + * drop reference of objpool anyway even if
> >> + * the obj is NULL, since one extra ref upon
> >> + * objpool was already grabbed during pool
> >> + * initialization in objpool_init()
> >> + */
> >> + if (refcount_dec_and_test(&pool->ref))
> >> + objpool_free(pool);
> >
> > Nit: you can call objpool_drop() instead of repeating the same thing here.
>
> objpool_drop won't deref objpool if given obj is NULL. But here we need
> drop objpool anyway even if obj is NULL.
I guess you decrement for the 'objpool' itself if obj=NULL, but I think
it is a bit hacky (so you added the comment).
e.g. rethook is doing something like below.
---
/* extra count for this pool itself */
count = 1;
/* make the pool empty */
while (objpool_pop(pool))
count++;
if (refcount_sub_and_test(count, &pool->ref))
objpool_free(pool);
---
>
> > Thank you,
> >
> >> + } while (obj);
> >> +}
> >> +EXPORT_SYMBOL_GPL(objpool_fini);
> >> --
> >> 2.40.1
> >>
>
> Thanks for you time
>
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2023-10-15 23:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-15 5:32 [PATCH v10 0/5] lib,kprobes: kretprobe scalability improvement wuqiang.matt
2023-10-15 5:32 ` [PATCH v10 1/5] lib: objpool added: ring-array based lockless MPMC wuqiang.matt
2023-10-15 15:43 ` Masami Hiramatsu
2023-10-15 16:06 ` wuqiang.matt
2023-10-15 23:26 ` Masami Hiramatsu [this message]
2023-10-16 2:45 ` wuqiang.matt
2023-10-16 12:18 ` Masami Hiramatsu
2023-10-16 15:00 ` wuqiang.matt
2023-10-16 15:04 ` wuqiang.matt
2023-10-16 17:05 ` wuqiang.matt
2023-10-17 1:27 ` Masami Hiramatsu
2023-10-15 5:32 ` [PATCH v10 2/5] lib: objpool test module added wuqiang.matt
2023-10-15 5:32 ` [PATCH v10 3/5] kprobes: kretprobe scalability improvement with objpool wuqiang.matt
2023-10-16 13:21 ` Masami Hiramatsu
2023-10-16 15:18 ` wuqiang.matt
2023-10-15 5:32 ` [PATCH v10 4/5] kprobes: freelist.h removed wuqiang.matt
2023-10-16 13:23 ` Masami Hiramatsu
2023-10-18 15:13 ` Masami Hiramatsu
2023-10-15 5:32 ` [PATCH v10 5/5] MAINTAINERS: objpool added wuqiang.matt
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=20231016082659.6ca94a5dff368783698753f9@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 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).