From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: "thomas@monjalon.net" <thomas@monjalon.net>,
"web@dpdk.org" <web@dpdk.org>
Cc: nd <nd@arm.com>
Subject: Re: [dpdk-web] [PATCH] update Arm roadmap for 19.05
Date: Tue, 12 Feb 2019 18:55:41 +0000 [thread overview]
Message-ID: <AM0PR08MB36676484B8EA3D63E082A5B398650@AM0PR08MB3667.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20190212185258.1916-1-thomas@monjalon.net>
> Arm roadmap is announced in the dpdk-dev mailing list:
> http://mails.dpdk.org/archives/dev/2019-February/124660.html
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
> content/roadmap/_index.md | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md index
> fb1fe8b..ccfcb63 100644
> --- a/content/roadmap/_index.md
> +++ b/content/roadmap/_index.md
> @@ -14,6 +14,10 @@ This list is obviously neither complete nor guaranteed.
> - new device specification (devargs) syntax
> - documentation for device management
> - DMA mapping API for external memory
> +- relaxed memory ordering in spinlock and rwlock
> +- ticket-lock
> +- RCU library
> +- lock-free extended bucket in hash library
Looks good.
Reviewed-by: Honnappa Nagarahalli <Honnappa.nagarahalli@arm.com>
> - TCP SEQ and ACK offload with rte_flow API and mlx5 implementation
> - ICMP ping offload with rte_flow API and mlx5 implementation
> - new mlx5 steering flow engine for high (millions/sec) insertion rate
> --
> 2.20.1
next prev parent reply other threads:[~2019-02-12 18:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 18:52 Thomas Monjalon
2019-02-12 18:55 ` Honnappa Nagarahalli [this message]
2019-02-12 20:18 ` 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=AM0PR08MB36676484B8EA3D63E082A5B398650@AM0PR08MB3667.eurprd08.prod.outlook.com \
--to=honnappa.nagarahalli@arm.com \
--cc=nd@arm.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).