DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
	Neil Horman <nhorman@tuxdriver.com>,
	John McNamara <john.mcnamara@intel.com>,
	Marko Kovacevic <marko.kovacevic@intel.com>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>,
	shahafs@mellanox.com
Subject: [dpdk-dev] [PATCH v2] doc: reduce initial offload API scope to drivers
Date: Fri, 13 Apr 2018 22:20:59 +0100	[thread overview]
Message-ID: <20180413212059.137738-1-ferruh.yigit@intel.com> (raw)
In-Reply-To: <20180316153141.124657-1-ferruh.yigit@intel.com>

Do ethdev new offloading API switch in two steps.

In v18.05 target is implementing the new ethdev-PMD offload interface,
which means converting all PMDs to new offloading API.

Next target is removing the old ethdev offload API.
It will effect applications and will force them to implement new
offloading API.

Fixes: 3004d3454192 ("doc: update deprecation of ethdev offload API")
Cc: shahafs@mellanox.com

Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
---
v2:
* Update commit log and deprecation notice for clarification
---
 doc/guides/rel_notes/deprecation.rst | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index c929dcc31..fd9def20c 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -72,8 +72,12 @@ 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 ethdev - drivers offload interface will be deprecated on 18.05.
+  This includes:
+  - removal of the conversion in ethdev from new offloading API to old API for drivers.
+
+  In later releases the old offloading API will be deprecated, 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.
-- 
2.14.3

  parent reply	other threads:[~2018-04-13 21:21 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
2018-04-13 21:20   ` Ferruh Yigit [this message]
2018-04-15  5:28     ` [dpdk-dev] [PATCH v2] " 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=20180413212059.137738-1-ferruh.yigit@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).