From: Bruce Richardson <bruce.richardson@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] deadline for 2.0 features proposal
Date: Tue, 3 Feb 2015 15:15:08 -0700 [thread overview]
Message-ID: <20150203221507.GA5476@bricha3-MOBL3> (raw)
In-Reply-To: <8420728.CIi4GzGLqo@xps13>
On Tue, Feb 03, 2015 at 09:24:28PM +0100, Thomas Monjalon wrote:
> 2015-02-03 12:04, Bruce Richardson:
> > On Tue, Feb 03, 2015 at 11:40:41AM +0100, Thomas Monjalon wrote:
> > > Hi,
> > >
> > > These features were planned in the 2.0 roadmap but not submitted:
> > > - cuckoo hash
> > > - packet distributor (phase 2)
> > > - bifurcated driver, assuming availability in Linux kernel
> > > - Broadcom driver
> > > - Hyper-V driver
> > > - i40e QoS
> > > - i40e IEEE1588
> > > - i40e DCB
> > > - i40e SR-IOV switching
> > > - i40e port mirroring
> > >
> > > They are now in the 2.1 roadmap.
> > > If you are working on one of these features or plan to do,
> > > please confirm their status and the estimated integration window.
> > >
> > > Thanks
> >
> > There are no enhancements to the packet distributor lib which will be ready for
> > inclusion inside the 2.0 timeframe.
>
> But there will be something new for 2.1?
> What means "phase 2"?
>
> Thanks
> --
> Thomas
I'm currently doing some investigation work in this area, to see what ways we
can improve performance or use other distribution schemes. Depending on what
comes out of the investigations, there may or may not be improvements to push
in the 2.1 timeframe. It's too early to know at this point.
Regards,
/Bruce
next prev parent reply other threads:[~2015-02-03 22:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 21:40 Thomas Monjalon
2015-02-03 10:40 ` Thomas Monjalon
2015-02-03 19:04 ` Bruce Richardson
2015-02-03 20:24 ` Thomas Monjalon
2015-02-03 22:15 ` Bruce Richardson [this message]
2015-02-04 13:55 ` Butler, Siobhan A
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=20150203221507.GA5476@bricha3-MOBL3 \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).