From: Thomas Monjalon <thomas@monjalon.net>
To: Shahaf Shuler <shahafs@mellanox.com>,
Ferruh Yigit <ferruh.yigit@intel.com>
Cc: John McNamara <john.mcnamara@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 5/6] doc: add offload flag to PMD todo list
Date: Wed, 22 Nov 2017 09:54:19 +0100 [thread overview]
Message-ID: <7543023.ylcdRrKDlW@xps> (raw)
In-Reply-To: <VI1PR05MB31498E1E4E174EC93A98C343C3200@VI1PR05MB3149.eurprd05.prod.outlook.com>
22/11/2017 09:43, Shahaf Shuler:
> Tuesday, November 21, 2017 8:03 PM, Ferruh Yigit:
> > On 11/21/2017 12:32 AM, Shahaf Shuler wrote:
> > >
> > > The deprecation of the old offloads API is set to 18.05 [1]. my
> > understanding was that we agreed to convert all PMDs on 18.02.
> > > If the PMD deadline is going to be postponed I think the ethdev
> > deprecation should be updated.
> >
> > Hi Shahaf,
> >
> > I put deadlines roughly and they need to be discussed here.
> >
> > But 18.02 deadline is not far away.
> > I think it is not realistic to expect all relevant PMDs do this conversion on
> > time, what do you think?
>
> I cannot tell about other vendors plans. For mlx4 and mlx5 I plan to convert on 18.02.
> From the discussion we had on 17.11 for this feature we agreed to split it into 2, and the PMD part will be on 18.02. no one objected.
>
> Maybe on the next Tech-board you can have a sync between some of the vendors to see the plans.
> If not all can make it, we should postpone the deprecation of the old API.
The current plan looks good to me.
We try to migrate to the new API in 18.02.
If some drivers are not migrated in 18.02, we urge them to do so in 18.05.
And we remove the old API in 18.05.
next prev parent reply other threads:[~2017-11-22 8:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 1:42 [dpdk-dev] [PATCH 1/6] doc: add empty PMDs " Ferruh Yigit
2017-11-21 1:42 ` [dpdk-dev] [PATCH 2/6] doc: add mbuf reorg to PMD " Ferruh Yigit
2017-12-11 14:00 ` Marko Kovacevic
2017-12-11 14:09 ` Mcnamara, John
2017-12-29 11:58 ` Andrew Rybchenko
2017-12-29 17:07 ` Stephen Hemminger
2018-01-03 14:00 ` Olivier Matz
2017-11-21 1:42 ` [dpdk-dev] [PATCH 3/6] doc: add dynamic logging " Ferruh Yigit
2017-12-08 5:12 ` Hemant Agrawal
2017-12-11 14:09 ` Mcnamara, John
2017-11-21 1:42 ` [dpdk-dev] [PATCH 4/6] doc: add descriptor status API " Ferruh Yigit
2017-12-11 14:11 ` Mcnamara, John
2017-11-21 1:42 ` [dpdk-dev] [PATCH 5/6] doc: add offload flag " Ferruh Yigit
2017-11-21 8:32 ` Shahaf Shuler
2017-11-21 18:02 ` Ferruh Yigit
2017-11-22 8:43 ` Shahaf Shuler
2017-11-22 8:54 ` Thomas Monjalon [this message]
2017-12-11 14:11 ` Mcnamara, John
2017-11-21 1:42 ` [dpdk-dev] [PATCH 6/6] doc: add mbuf VLAN " Ferruh Yigit
2017-11-21 1:53 ` Ferruh Yigit
2017-12-06 9:24 ` Hemant Agrawal
2017-12-11 14:16 ` Mcnamara, John
2017-12-29 11:50 ` Andrew Rybchenko
2017-12-29 17:09 ` Stephen Hemminger
2018-01-03 14:14 ` Olivier Matz
2017-12-11 11:52 ` [dpdk-dev] [PATCH 1/6] doc: add empty PMDs " Mcnamara, John
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=7543023.ylcdRrKDlW@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=shahafs@mellanox.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).