DPDK patches and discussions
 help / color / mirror / Atom feed
From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: "dev@dpdk.org" <dev@dpdk.org>,
	"thomas@monjalon.net" <thomas@monjalon.net>,
	David Marchand <david.marchand@redhat.com>
Cc: Ruifeng Wang <Ruifeng.Wang@arm.com>, nd <nd@arm.com>, nd <nd@arm.com>
Subject: Arm roadmap for 22.03
Date: Fri, 7 Jan 2022 17:15:43 +0000	[thread overview]
Message-ID: <DBAPR08MB5814A8FBF20C303FC990DE60984D9@DBAPR08MB5814.eurprd08.prod.outlook.com> (raw)

(Bcc: Arm internal stake holders)

Hello,
	Following are the work items planned for 22.03:

1) Index based per core mempool cache
2) Direct-rearm of RX side buffers

Both the changes are in the mailing list already[1][2]. Along with these, there will be few minor patches to fix bugs.

Please let me know if there are any questions.

Thank you,
Honnappa

[1] http://patches.dpdk.org/project/dpdk/cover/20211224225923.806498-1-dharmik.thakkar@arm.com/
[2] http://patches.dpdk.org/project/dpdk/cover/20211224164613.32569-1-feifei.wang2@arm.com/


                 reply	other threads:[~2022-01-07 17:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=DBAPR08MB5814A8FBF20C303FC990DE60984D9@DBAPR08MB5814.eurprd08.prod.outlook.com \
    --to=honnappa.nagarahalli@arm.com \
    --cc=Ruifeng.Wang@arm.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=nd@arm.com \
    --cc=thomas@monjalon.net \
    /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).