From: Thomas Monjalon <thomas@monjalon.net>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: web@dpdk.org, david.marchand@redhat.com,
honnappa.nagarahalli@arm.com, niklas.soderlund@corigine.com,
liudongdong3@huawei.com, jerinj@marvell.com,
lmargalit@nvidia.com
Subject: Re: [PATCH 7/7] update SmartShare Systems roadmap for 22.11
Date: Sun, 27 Nov 2022 23:05:32 +0100 [thread overview]
Message-ID: <1938144.CrzyxZ31qj@thomas> (raw)
In-Reply-To: <000001d902aa$13e2a855$0a04a8c0@smartsharesys.local>
27/11/2022 22:49, Morten Brørup:
> mempool stats without debug overheadMade it into 22.11 in the last minute.
Yes
With the cache optimization, it is described as "mempool optimizations" in the announce.
next prev parent reply other threads:[~2022-11-27 22:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-27 21:49 Morten Brørup
2022-11-27 22:05 ` Thomas Monjalon [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-27 20:12 [PATCH 0/7] 22.11 roadmaps Thomas Monjalon
2022-11-27 20:12 ` [PATCH 7/7] update SmartShare Systems roadmap for 22.11 Thomas Monjalon
2022-11-27 20:43 ` Morten Brørup
2022-11-27 21:34 ` Thomas Monjalon
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=1938144.CrzyxZ31qj@thomas \
--to=thomas@monjalon.net \
--cc=david.marchand@redhat.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=jerinj@marvell.com \
--cc=liudongdong3@huawei.com \
--cc=lmargalit@nvidia.com \
--cc=mb@smartsharesystems.com \
--cc=niklas.soderlund@corigine.com \
--cc=web@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;
as well as URLs for NNTP newsgroup(s).