From: Shahaf Shuler <shahafs@mellanox.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Guidelines for moving PMDs to new ethdev offloads API
Date: Sun, 10 Dec 2017 06:04:45 +0000 [thread overview]
Message-ID: <VI1PR05MB3149450ECF26C2A7C327F14EC3360@VI1PR05MB3149.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20171209215211.4374b057@xeon-e3>
Sunday, December 10, 2017 7:52 AM, Stephen Hemminger:
>
> On Sun, 10 Dec 2017 05:35:45 +0000
> Shahaf Shuler <shahafs@mellanox.com> wrote:
>
> > In 17.11 the ethdev offloads API has changed:
> >
> > commit cba7f53b717d ("ethdev: introduce Tx queue offloads API")
> >
> > commit ce17eddefc20 ("ethdev: introduce Rx queue offloads API")
> The new API is documented in the programmer's guide:
> >
> >
> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdpd
> k.org%2Fdoc%2Fguides%2Fprog_guide%2Fpoll_mode_drv.html%23hardwar
> e-
> offload&data=02%7C01%7Cshahafs%40mellanox.com%7Cc365451c3f934b73d
> b5e08d53f6fe6fd%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636
> 484672216209911&sdata=l0OkZ8m78BMsw%2F0d7bA8m80gVqlSL%2Bpcs9Up
> lVSmlOA%3D&reserved=0
> >
> >
> >
> > As announced in the deprecation notice, the old API is planned to be
> removed in 18.05:
> >
> >
> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdpd
> k.org%2Fdoc%2Fguides%2Frel_notes%2Fdeprecation.html&data=02%7C01%
> 7Cshahafs%40mellanox.com%7Cc365451c3f934b73db5e08d53f6fe6fd%7Ca65
> 2971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636484672216209911&sdata
> =85wB%2BoU3um%2BXegYiLAJIDYWIkvpb9WQtPSgA73zsLHI%3D&reserved=
> 0
> >
[.. ]
>
> I agree with this change. but how can it be done with out breaking ABI?
Not sure I understand.
The new API has already been accepted on 17.11.
you mean the deprecation in 18.05? This also been accepted during 17.11 release.
next prev parent reply other threads:[~2017-12-10 6:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-10 5:35 Shahaf Shuler
2017-12-10 5:52 ` Stephen Hemminger
2017-12-10 6:04 ` Shahaf Shuler [this message]
2017-12-10 11:23 ` 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=VI1PR05MB3149450ECF26C2A7C327F14EC3360@VI1PR05MB3149.eurprd05.prod.outlook.com \
--to=shahafs@mellanox.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).