From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Thomas Monjalon" <thomas@monjalon.net>, <web@dpdk.org>
Cc: <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 21:43:47 +0100 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35D87515@smartserver.smartshare.dk> (raw)
In-Reply-To: <20221127201245.884619-8-thomas@monjalon.net>
> ### Version 22.11 (2022 November) {#2211}
>
> <!-- General -->
> +- non-temporal memory copy
I'm sorry, we didn't finish the non-temporal memory copy feature in time for 22.11.
We have not given up on it, so please move it down under the "Nice to have - Future" headline instead.
However, consider adding [1] (feel free to rephrase):
- mempool stats without debug overhead
[1]: https://patchwork.dpdk.org/project/dpdk/list/?series=25670&state=3
> - index-based per core mempool cache
The index-based mempool cache did not make it due to ABI breakage, and should probably be removed from the list.
This contribution came from ARM, perhaps @Honnappa has an opinion?
next prev parent reply other threads:[~2022-11-27 20:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-27 20:12 [PATCH 0/7] 22.11 roadmaps Thomas Monjalon
2022-11-27 20:12 ` [PATCH 1/7] update DTS roadmap for 22.11 Thomas Monjalon
2022-11-27 20:12 ` [PATCH 2/7] update Arm " Thomas Monjalon
2022-11-27 20:12 ` [PATCH 3/7] update Corigine " Thomas Monjalon
2022-11-27 20:12 ` [PATCH 4/7] update Huawei " Thomas Monjalon
2022-11-27 20:12 ` [PATCH 5/7] update Marvell " Thomas Monjalon
2022-11-27 20:12 ` [PATCH 6/7] update NVIDIA " Thomas Monjalon
2022-11-27 20:12 ` [PATCH 7/7] update SmartShare Systems " Thomas Monjalon
2022-11-27 20:43 ` Morten Brørup [this message]
2022-11-27 21:34 ` Thomas Monjalon
2022-11-27 21:49 Morten Brørup
2022-11-27 22:05 ` 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=98CBD80474FA8B44BF855DF32C47DC35D87515@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=david.marchand@redhat.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=jerinj@marvell.com \
--cc=liudongdong3@huawei.com \
--cc=lmargalit@nvidia.com \
--cc=niklas.soderlund@corigine.com \
--cc=thomas@monjalon.net \
--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).