From: "Morten Brørup" <mb@smartsharesystems.com>
To: <dev@dpdk.org>
Cc: "Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>
Subject: RE: [RFC PATCH v3 1/2] mempool: simplify get objects
Date: Fri, 13 Mar 2026 16:36:02 +0100 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35F65791@smartserver.smartshare.dk> (raw)
In-Reply-To: <24cc7908-f8f4-4bbe-944f-885169f0f68b@oktetlabs.ru>
> From: Andrew Rybchenko [mailto:andrew.rybchenko@oktetlabs.ru]
> Sent: Tuesday, 17 February 2026 07.19
>
> Hi Morten,
>
> On 2/16/26 6:23 PM, Morten Brørup wrote:
> > Removed explicit test for build time constant request size,
> > and added comment that the compiler loop unrolls when request size is
> > build time constant, to improve source code readability.
> >
> > Moved setting cache->len up before the copy loop; not only for code
> > similarity (cache->len is now set before each copy loop), but also as
> an
> > optimization:
> > The function's pointer parameters are not marked restrict, so writing
> to
> > obj_table in the copy loop might formally modify cache->size. And
> thus,
> > setting cache->len = cache->size after the copy loop requires loading
> > cache->size again after copying the objects.
> > Moving this line up before the copy loop avoids that extra load of
> > cache->size when setting cache->len.
> >
> > Similarly, moved statistics update up before the copy loops.
> >
> > Signed-off-by: Morten Brørup <mb@smartsharesystems.com>
>
> LGTM, the result looks simpler, easier to read and understand.
> If there is no measurable performance degradation after the patch
>
> Reviewed-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
>
There's a real patch [1] for this RFC patch 1/2.
Marking this RFC patch 1/2 as Superseded.
[1]: https://patchwork.dpdk.org/project/dpdk/patch/20260216092750.94137-1-mb@smartsharesystems.com/
next prev parent reply other threads:[~2026-03-13 15:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 11:58 [RFC PATCH 0/2] mempool: de-inline get/put objects unlikely code Morten Brørup
2026-02-16 11:58 ` [RFC PATCH 1/2] mempool: simplify get objects Morten Brørup
2026-02-16 11:58 ` [RFC PATCH 2/2] mempool: de-inline get/put objects unlikely code paths Morten Brørup
2026-02-16 13:13 ` [RFC PATCH v2 0/2] mempool: de-inline get/put objects unlikely code Morten Brørup
2026-02-16 13:13 ` [RFC PATCH v2 1/2] mempool: simplify get objects Morten Brørup
2026-02-16 13:13 ` [RFC PATCH v2 2/2] mempool: de-inline get/put objects unlikely code paths Morten Brørup
2026-02-16 15:23 ` [RFC PATCH v3 0/2] mempool: de-inline get/put " Morten Brørup
2026-02-16 15:23 ` [RFC PATCH v3 1/2] mempool: simplify get objects Morten Brørup
2026-02-17 6:19 ` Andrew Rybchenko
2026-03-13 15:36 ` Morten Brørup [this message]
2026-02-16 15:23 ` [RFC PATCH v3 2/2] mempool: de-inline get/put unlikely code paths Morten Brørup
2026-02-16 17:35 ` Stephen Hemminger
2026-02-16 19:59 ` Morten Brørup
2026-02-17 6:37 ` Andrew Rybchenko
2026-03-13 15:27 ` Morten Brørup
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=98CBD80474FA8B44BF855DF32C47DC35F65791@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.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