From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Shahaf Shuler <shahafs@mellanox.com>,
Neil Horman <nhorman@tuxdriver.com>,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH] doc: reduce initial offload API scope to drivers
Date: Tue, 20 Mar 2018 14:02:55 +0000 [thread overview]
Message-ID: <6e80ead7-05b4-1724-6427-a01269134c84@intel.com> (raw)
In-Reply-To: <DB7PR05MB4426388F64BA6DC91B494D53C3D50@DB7PR05MB4426.eurprd05.prod.outlook.com>
On 3/18/2018 5:57 AM, Shahaf Shuler wrote:
> Hi Ferruh,
>
> Friday, March 16, 2018 5:32 PM, Ferruh Yigit:
>> Subject: [PATCH] doc: reduce initial offload API scope to drivers
>>
>> 18.05 tagets ethdev-PMD offload API, which means switching all PMDs to
>> new offloading API
>>
>> Next step targets ethdev-application offload API which means forcing
>> applications to switch to new API
>>
>> Fixes: 3004d3454192 ("doc: update deprecation of ethdev offload API")
>> Cc: shahafs@mellanox.com
>>
>> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
>> ---
>> doc/guides/rel_notes/deprecation.rst | 7 ++++++-
>> 1 file changed, 6 insertions(+), 1 deletion(-)
>>
>> diff --git a/doc/guides/rel_notes/deprecation.rst
>> b/doc/guides/rel_notes/deprecation.rst
>> index 0c696f743..b40c57f28 100644
>> --- a/doc/guides/rel_notes/deprecation.rst
>> +++ b/doc/guides/rel_notes/deprecation.rst
>> @@ -97,8 +97,13 @@ Deprecation Notices
>> * ethdev: a new Tx and Rx offload API was introduced on 17.11.
>> In the new API, offloads are divided into per-port and per-queue offloads.
>> Offloads are disabled by default and enabled per application request.
>> - The old offloads API is target to be deprecated on 18.05. This includes:
>> + The old offloads API between ethdev and drivers is target to be
>> deprecated on 18.05.
>> + This includes:
>>
>> + - removal of the conversion in ethdev from new offloading API to old API.
>
> We cannot remove this part before all of the applications has moved to the new API.
> The conversion function is to help PMDs to have single control path with no branch for both old and new application.
There are two conversion done in ethdev:
1) From old API to new API
2) From new API to old API
so that PMDs can have access to both old and new API independent from what
application provided.
Above text suggesting to remove only 2).
If we switch all PMDs to new API we don't need conversion 2) anymore.
If application using new API we are all good, for old application that using old
API ethdev will convert to new API so that PMDs can use them.
>
>> +
>> + In later releases the old offloading API between ethdev and
>> + applications will be deprecated too, which will include:
>> - removal of ``ETH_TXQ_FLAGS_NO*`` flags.
>> - removal of ``txq_flags`` field from ``rte_eth_txconf`` struct.
>> - removal of the offloads bit-field from ``rte_eth_rxmode`` struct.
>
> I am OK with postponing the deprecation to a later release and have the PMDs conversion to the new API in the current/next one.
>
>> --
>> 2.13.6
>
next prev parent reply other threads:[~2018-03-20 14:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 14:24 [dpdk-dev] [PATCH] doc: update deprecation of ethdev offload API Shahaf Shuler
2017-10-25 10:49 ` Shahaf Shuler
2017-11-08 11:16 ` Andrew Rybchenko
2017-11-10 16:41 ` Ananyev, Konstantin
2017-11-12 4:19 ` Thomas Monjalon
2018-03-16 15:31 ` [dpdk-dev] [PATCH] doc: reduce initial offload API scope to drivers Ferruh Yigit
2018-03-18 5:57 ` Shahaf Shuler
2018-03-20 14:02 ` Ferruh Yigit [this message]
2018-04-13 21:20 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2018-04-15 5:28 ` Shahaf Shuler
2018-04-15 13:14 ` 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=6e80ead7-05b4-1724-6427-a01269134c84@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=nhorman@tuxdriver.com \
--cc=shahafs@mellanox.com \
--cc=thomas@monjalon.net \
/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).