DPDK website maintenance
 help / color / mirror / Atom feed
From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Thomas Monjalon" <thomas@monjalon.net>
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 22:49:06 +0100	[thread overview]
Message-ID: <000001d902aa$13e2a855$0a04a8c0@smartsharesys.local> (raw)

[-- Attachment #1: Type: text/plain, Size: 1392 bytes --]

mempool stats without debug overheadMade it into 22.11 in the last minute.-MortenSent from smartphone. Please excuse brevity and spelling.
-------- Oprindelig besked --------Fra: Thomas Monjalon <thomas@monjalon.net> Dato: 27.11.2022  22.34  (GMT+01:00) Til: 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 Emne: Re: [PATCH 7/7] update SmartShare Systems roadmap for 22.11 27/11/2022 21:43, Morten Brørup:> >  ### 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.It is moved to 23.03 in a following patch.> However, consider adding [1] (feel free to rephrase):>  - mempool stats without debug overheadYou can add it to the roadmap for 23.03.> [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?Let's refresh the list for the next releases.

[-- Attachment #2: Type: text/html, Size: 2197 bytes --]

             reply	other threads:[~2022-11-27 21:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-27 21:49 Morten Brørup [this message]
2022-11-27 22:05 ` Thomas Monjalon
  -- 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='000001d902aa$13e2a855$0a04a8c0@smartsharesys.local' \
    --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).