All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Rybchenko <arybchenko@solarflare.com>
To: Thomas Monjalon <thomas@monjalon.net>, <ferruh.yigit@intel.com>,
	<shahafs@mellanox.com>
Cc: <dev@dpdk.org>, <ravi1.kumar@amd.com>, <rasesh.mody@cavium.com>,
	<maxime.coquelin@redhat.com>
Subject: Re: [PATCH v2 5/5] ethdev: remove old offload API
Date: Wed, 4 Jul 2018 14:31:24 +0300	[thread overview]
Message-ID: <9a853bb4-b20a-0690-5ecf-da8c5fd24560@solarflare.com> (raw)
In-Reply-To: <20180702212750.16758-6-thomas@monjalon.net>

On 07/03/2018 12:27 AM, Thomas Monjalon wrote:
> From: Ferruh Yigit <ferruh.yigit@intel.com>
>
> In DPDK 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:
> 	http://doc.dpdk.org/guides/prog_guide/poll_mode_drv.html#hardware-offload
>
> For reminder, the main concepts in the new API were:
> 	- All offloads are disabled by default
> 	- Distinction between per port and per queue offloads.
>
> The transition bits are now removed:
> 	- Translation of the old API in ethdev
> 	- rte_eth_conf.rxmode.ignore_offload_bitfield
> 	- ETH_TXQ_FLAGS_IGNORE
>
> The old API bits are now removed:
> 	- Rx per-port rte_eth_conf.rxmode.[bit-fields]
> 	- Tx per-queue rte_eth_txconf.txq_flags
> 	- ETH_TXQ_FLAGS_NO*
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---

Reviewed-by: Andrew Rybchenko <arybchenko@solarflare.com>

  parent reply	other threads:[~2018-07-04 11:31 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-08 22:41 [RFC] ethdev: remove all offload API Ferruh Yigit
2018-06-08 21:52 ` Ferruh Yigit
2018-06-09  8:04 ` Andrew Rybchenko
2018-06-11  9:09   ` Ferruh Yigit
2018-06-11 11:00     ` Shahaf Shuler
2018-06-11 11:18       ` Ferruh Yigit
2018-06-11 11:26         ` Ananyev, Konstantin
2018-06-11 11:35           ` Ferruh Yigit
2018-06-11 11:35           ` Shahaf Shuler
2018-06-11 12:12             ` Ferruh Yigit
2018-06-29  1:11 ` Thomas Monjalon
2018-07-02 21:27   ` [PATCH v2 0/5] remove old ethdev " Thomas Monjalon
2018-07-02 21:27     ` [PATCH v2 1/5] doc: remove code from KNI example guide Thomas Monjalon
2018-07-02 21:27     ` [PATCH v2 2/5] test: remove unused configuration for bonding Thomas Monjalon
2018-07-02 21:27     ` [PATCH v2 3/5] ethdev: convert remaining apps to new offload API Thomas Monjalon
2018-07-04 11:16       ` Andrew Rybchenko
2018-07-04 12:26         ` Thomas Monjalon
2018-07-04 12:52           ` Andrew Rybchenko
2018-07-02 21:27     ` [PATCH v2 4/5] net/fm10k: remove unused constant Thomas Monjalon
2018-07-02 21:27     ` [PATCH v2 5/5] ethdev: remove old offload API Thomas Monjalon
2018-07-03 12:28       ` Shahaf Shuler
2018-07-04 11:31       ` Andrew Rybchenko [this message]
2018-07-03 18:37     ` [PATCH v2 0/5] remove old ethdev " Ferruh Yigit
2018-07-04 18:56       ` Ferruh Yigit
2018-07-02 21:34   ` [RFC] ethdev: remove all " 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=9a853bb4-b20a-0690-5ecf-da8c5fd24560@solarflare.com \
    --to=arybchenko@solarflare.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=rasesh.mody@cavium.com \
    --cc=ravi1.kumar@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.