From: Thomas Monjalon <thomas@monjalon.net>
To: mb@smartsharesystems.com, olivier.matz@6wind.com,
konstantin.v.ananyev@yandex.ru, honnappa.nagarahalli@arm.com
Cc: dev@dpdk.org, ruifeng.wang@arm.com,
kamalakshitha.aligeri@arm.com, wathsala.vithanage@arm.com,
nd@arm.com
Subject: Re: [PATCH 0/4] Small corrections in mempool
Date: Wed, 07 Jun 2023 11:35:20 +0200 [thread overview]
Message-ID: <84309111.BzKH3j3Lxt@thomas> (raw)
In-Reply-To: <20230309045738.1261000-1-honnappa.nagarahalli@arm.com>
Any update about this series?
09/03/2023 05:57, Honnappa Nagarahalli:
> 1) Patches 1/4, 2/4 - Few small corrections in mempool API documentation.
> 2) Patch 3/4 - The API for checking 'lcore ID is valid' is trivial,
> but it is the right thing to do.
> 3) Patch 4/4 - IMO, the 'lcore ID is valid' check is not necessary to be
> done during run time. If it is not valid, there is something seriously
> wrong in the system already or it is a programming error. Given that
> it is a data plane function, it makes sense to remove it from run
> time check.
>
> Honnappa Nagarahalli (4):
> mempool: clarify mempool cache flush API behavior
> mempool: clarify comments for mempool cache implementation
> eal: add API to check if lcore id is valid
> mempool: use lcore API to check if lcore ID is valid
>
> lib/eal/include/rte_lcore.h | 14 ++++++++++++++
> lib/mempool/rte_mempool.c | 12 ++++++------
> lib/mempool/rte_mempool.h | 13 ++++++++-----
> 3 files changed, 28 insertions(+), 11 deletions(-)
prev parent reply other threads:[~2023-06-07 9:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 4:57 [PATCH 0/4] Small corrections in mempool Honnappa Nagarahalli
2023-03-09 4:57 ` [PATCH 1/4] mempool: clarify mempool cache flush API behavior Honnappa Nagarahalli
2023-06-07 10:03 ` Morten Brørup
2023-03-09 4:57 ` [PATCH 2/4] mempool: clarify comments for mempool cache implementation Honnappa Nagarahalli
2023-06-07 10:10 ` Morten Brørup
2024-10-04 21:08 ` Stephen Hemminger
2023-03-09 4:57 ` [PATCH 3/4] eal: add API to check if lcore id is valid Honnappa Nagarahalli
2023-06-07 10:19 ` Morten Brørup
2023-06-07 15:05 ` Stephen Hemminger
2023-03-09 4:57 ` [PATCH 4/4] mempool: use lcore API to check if lcore ID " Honnappa Nagarahalli
2023-03-09 9:39 ` Konstantin Ananyev
2023-03-10 4:01 ` Honnappa Nagarahalli
2023-03-10 14:06 ` Konstantin Ananyev
2023-06-07 9:35 ` Thomas Monjalon [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=84309111.BzKH3j3Lxt@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
--cc=kamalakshitha.aligeri@arm.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=mb@smartsharesystems.com \
--cc=nd@arm.com \
--cc=olivier.matz@6wind.com \
--cc=ruifeng.wang@arm.com \
--cc=wathsala.vithanage@arm.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.