From: "Hunt, David" <david.hunt@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
"O'Driscoll, Tim" <tim.odriscoll@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] 17.02 Roadmap
Date: Thu, 13 Oct 2016 15:18:31 +0100 [thread overview]
Message-ID: <c92322c9-a8a4-8a9b-54b9-6fc1b403f986@intel.com> (raw)
In-Reply-To: <1998191.9HGrB6oKr3@xps13>
Hi Thomas,
On 10/10/2016 9:42 PM, Thomas Monjalon wrote:
> Thanks Tim for the interesting inputs.
> Some of them may require a dedicated thread to continue the discussion
> based on some preliminary specifications or drafts.
>
> 2016-10-10 16:13, O'Driscoll, Tim:
>> Packet Distributor Enhancements: Enhancements will be made to the Packet Distributor library to improve performance:
>> 1. Introduce burst functionality to allow batches of packets to be sent to workers.
>> 2. Improve the performance of the flow/core affinity through the use of SSE/AVX instructions.
> The packet distributor looks more and more like a DPDK application
> at the same level of BESS, VPP, OVS, etc.
Lets discuss this further. Would you see other libraries heading in
this direction also (reorder, acl, hash, etc)?
Do you think it would be an idea to add as an item of discussion for the
technical steering group when we're all at Userspace next week?
Regards,
Dave.
next prev parent reply other threads:[~2016-10-13 14:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 16:13 O'Driscoll, Tim
2016-10-10 20:42 ` Thomas Monjalon
2016-10-11 5:32 ` Yuanhan Liu
2016-10-11 9:09 ` O'Driscoll, Tim
2016-10-11 10:25 ` Pattan, Reshma
2016-10-11 22:36 ` De Lara Guarch, Pablo
2016-10-13 3:15 ` Tan, Jianfeng
2016-10-13 14:18 ` Hunt, David [this message]
2016-10-13 14:39 ` Thomas Monjalon
2016-10-14 17:29 ` Stephen Hemminger
2016-10-14 20:18 ` Thomas Monjalon
2016-10-16 20:21 ` O'Driscoll, Tim
-- strict thread matches above, loose matches on Subject: below --
2016-08-31 10:31 O'Driscoll, Tim
2016-08-31 12:07 ` 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=c92322c9-a8a4-8a9b-54b9-6fc1b403f986@intel.com \
--to=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.com \
--cc=tim.odriscoll@intel.com \
/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).