From: Thomas Monjalon <thomas@monjalon.net>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: "Kovacevic, Marko" <marko.kovacevic@intel.com>,
"web@dpdk.org" <web@dpdk.org>,
"O'Driscoll, Tim" <tim.odriscoll@intel.com>
Subject: Re: [dpdk-web] [PATCH] update Intel roadmap for 19.05
Date: Mon, 18 Feb 2019 15:51:48 +0100 [thread overview]
Message-ID: <20953894.L8HUZOpLqN@xps> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE23F5542FF@IRSMSX103.ger.corp.intel.com>
18/02/2019 13:30, Mcnamara, John:
> > -----Original Message-----
> > From: Thomas Monjalon [mailto:thomas@monjalon.net]
> > Sent: Friday, February 15, 2019 9:06 PM
> > To: Kovacevic, Marko <marko.kovacevic@intel.com>
> > Cc: web@dpdk.org; Mcnamara, John <john.mcnamara@intel.com>; O'Driscoll,
> > Tim <tim.odriscoll@intel.com>
> > Subject: Re: [PATCH] update Intel roadmap for 19.05
> >
> > 15/02/2019 17:43, Marko Kovacevic:
> > > Intel roadmap is announced in the dpdk-dev mailing list:
> > > http://mails.dpdk.org/archives/dev/2019-February/124766.html
> > >
> > > Signed-off-by: Marko Kovacevic <marko.kovacevic@intel.com>
> > > ---
> > > +- QAT asymmetric crypto with support for modexp and modinv
> > > +- QAT compression PMD support for large scatter-gather lists
> > > +- add a DPDK PMD to support AF_XDP
> > > +- support for additional crypto/auth algorithms in the ipsec library
> > > +- initial support for DPDK on Windows
> > > +- add new baseband device turbo PMD
> >
> > I changed the order to sort it like in the release notes, and did few
> > small rewords, hence
> > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> >
> > and applied: http://core.dpdk.org/roadmap/
> >
> > I'm surprised you did not mention
> > virtio optimisations and non-blocking stack mempool handler.
> > Is there any specific reason?
>
> Hi,
>
> I left out the virtio optimization because I wasn't sure if they were large enough to mention.
>
> I left of the non-blocking stack mempool handler because it is being submitted by a different (Intel) team but I probably should have included it.
Feel free to update anything you think required.
prev parent reply other threads:[~2019-02-18 14:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 16:43 Marko Kovacevic
2019-02-15 21:05 ` Thomas Monjalon
2019-02-18 12:30 ` Mcnamara, John
2019-02-18 14:51 ` 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=20953894.L8HUZOpLqN@xps \
--to=thomas@monjalon.net \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=tim.odriscoll@intel.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).