From: Andrew Rybchenko <arybchenko@solarflare.com>
To: Qi Zhang <qi.z.zhang@intel.com>, <ferruh.yigit@intel.com>,
<konstantin.ananyev@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] ethdev: convert Tx offloads to Tx queue config
Date: Thu, 3 May 2018 12:24:34 +0300 [thread overview]
Message-ID: <c1dc17ef-175f-a029-427b-c4e13b8cd79e@solarflare.com> (raw)
In-Reply-To: <20180503060325.153722-1-qi.z.zhang@intel.com>
On 05/03/2018 09:03 AM, Qi Zhang wrote:
> Tx offload will be converted to txq_flags automatically during
> rte_eth_dev_info_get and rte_eth_tx_queue_info_get. So PMD can
> clean the code to get rid of txq_flags at all while keep old APP
> not be impacted.
>
> Signed-off-by: Qi Zhang <qi.z.zhang@intel.com>
It is a step in right direction. It allows net/sfc to cut the code which
fills in txq_flags in default TxQ config.
Tested-by: Andrew Rybchenko <arybchenko@solarflare.com>
next prev parent reply other threads:[~2018-05-03 9:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 6:03 Qi Zhang
2018-05-03 9:24 ` Andrew Rybchenko [this message]
2018-05-04 13:59 ` Ferruh Yigit
2018-05-04 14:00 ` Ferruh Yigit
2018-05-03 12:32 ` Ananyev, Konstantin
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=c1dc17ef-175f-a029-427b-c4e13b8cd79e@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=qi.z.zhang@intel.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).