From: Shahaf Shuler <shahafs@mellanox.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
Rafal Kozik <rk@semihalf.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "mw@semihalf.com" <mw@semihalf.com>,
"mk@semihalf.com" <mk@semihalf.com>,
"gtzalik@amazon.com" <gtzalik@amazon.com>,
"evgenys@amazon.com" <evgenys@amazon.com>,
"matua@amazon.com" <matua@amazon.com>,
"igorch@amazon.com" <igorch@amazon.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] net/ena: convert to new Tx offloads API
Date: Thu, 18 Jan 2018 06:26:19 +0000 [thread overview]
Message-ID: <VI1PR05MB31493CDB377B149443457727C3E80@VI1PR05MB3149.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <40a3b871-094f-0873-789d-d24a5ad4dc19@intel.com>
Wednesday, January 17, 2018 8:58 PM, Ferruh Yigit :
> > Here is it better to check also the ETH_TXQ_FLAGS_IGNORE.
> > If application has not yet moved to the new API, then it won't set any port
> Tx offloads. So for old applications, the
> ena_are_tx_queue_offloads_allowed is not necessary.
>
> But ethdev layer will set the offloads if ETH_TXQ_FLAGS_IGNORE is missing,
> can't PMD always only rely on tx_conf->offloads ?
This is to address PMD which moved to the new offloads API but the application still uses the old offloads API.
There are many Tx offloads which are per port (as there is a burst function per port, and not per queue). However the application will not set any offload on the device configuration rather only in the queue setup. The PMD can fail the setup function on such case, as per-port offload is requested on the queue setup without being requested first on the device configuration.
next prev parent reply other threads:[~2018-01-18 6:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 11:52 [dpdk-dev] [PATCH 0/2] net/ena: convert to new " Rafal Kozik
2018-01-16 11:52 ` [dpdk-dev] [PATCH 1/2] net/ena: convert to new Tx " Rafal Kozik
2018-01-17 6:56 ` Shahaf Shuler
2018-01-17 18:58 ` Ferruh Yigit
2018-01-18 6:26 ` Shahaf Shuler [this message]
2018-01-18 14:49 ` Ferruh Yigit
2018-01-17 8:23 ` [dpdk-dev] [PATCH v2 " Rafal Kozik
2018-01-17 18:58 ` Ferruh Yigit
2018-01-18 9:18 ` Rafał Kozik
2018-01-18 14:49 ` Ferruh Yigit
2018-01-18 14:53 ` Ferruh Yigit
2018-01-18 14:59 ` Michał Krawczyk
2018-01-18 15:12 ` Ferruh Yigit
2018-01-16 11:52 ` [dpdk-dev] [PATCH 2/2] net/ena: convert to new Rx " Rafal Kozik
2018-01-17 6:57 ` Shahaf Shuler
2018-01-17 8:26 ` [dpdk-dev] [PATCH v2 " Rafal Kozik
2018-01-18 15:06 ` Michał Krawczyk
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=VI1PR05MB31493CDB377B149443457727C3E80@VI1PR05MB3149.eurprd05.prod.outlook.com \
--to=shahafs@mellanox.com \
--cc=dev@dpdk.org \
--cc=evgenys@amazon.com \
--cc=ferruh.yigit@intel.com \
--cc=gtzalik@amazon.com \
--cc=igorch@amazon.com \
--cc=matua@amazon.com \
--cc=mk@semihalf.com \
--cc=mw@semihalf.com \
--cc=rk@semihalf.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).