From: Thomas Monjalon <thomas@monjalon.net>
To: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Cc: web@dpdk.org, nd@arm.com
Subject: Re: [dpdk-web] [PATCH] update Arm roadmap for 20.11
Date: Wed, 23 Sep 2020 23:42:57 +0200 [thread overview]
Message-ID: <2494563.7SuhCNyob0@thomas> (raw)
In-Reply-To: <20200911050057.25357-1-honnappa.nagarahalli@arm.com>
> <!-- General -->
> - x86 direct-store (write-combined) memory write (movdiri)
> - Arm CRC32 in generic API
> +- Scatter-Gather APIs for rte_ring
> +- Integrate RCU deferred resource reclamation APIs with rte_hash library
> +- Performance improvements to rte_stack library
> +- Use C11 atomic builtins in rte_bbdev, rte_eal, rte_ethdev and rte_power
Removed rte_ prefix to make it shorter, easier to read.
> libraries>
> <!-- Networking -->
> - FIB vector lookup
> - Tx QoS marking API
> @@ -24,12 +28,14 @@ This list is obviously neither complete nor guaranteed.
> - octeontx2 packet mirroring
> - octeontx2 rte_tm enhancement
> - qede SR-IOV PF
> +- deprecate rte_cio barrier APIs
Removed this one (neither a feature nor a major milestone).
Applied, thanks
prev parent reply other threads:[~2020-09-23 21:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 5:00 Honnappa Nagarahalli
2020-09-23 21:42 ` 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=2494563.7SuhCNyob0@thomas \
--to=thomas@monjalon.net \
--cc=honnappa.nagarahalli@arm.com \
--cc=nd@arm.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).