From: Alejandro Lucero <alejandro.lucero@netronome.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/nfp: support new HW offloads API
Date: Sat, 31 Mar 2018 17:53:35 +0100 [thread overview]
Message-ID: <CAD+H990MftyWwLSCzfK07PzwsgY1rSA+5JdSPGDKywHbNBP3HQ@mail.gmail.com> (raw)
In-Reply-To: <1c209b93-bdba-cff7-cb70-4971e80997d0@intel.com>
On Tue, Mar 27, 2018 at 7:25 PM, Ferruh Yigit <ferruh.yigit@intel.com>
wrote:
> On 3/15/2018 2:30 PM, Alejandro Lucero wrote:
> > In next 18.05 the old hw offload API will be removed. This patch adds
> > support for just the new hw offload API.
> >
> > Signed-off-by: Alejandro Lucero <alejandro.lucero@netronome.com>
>
> <...>
>
> > - if (rxmode->enable_scatter) {
> > + if (!(rxmode->offloads & DEV_RX_OFFLOAD_CRC_STRIP))
> > + PMD_INIT_LOG(INFO, "HW does strip CRC. No configurable!");
>
> Also this behavior is changing, not providing CRC_STRIP will be by default
> stripping [2], this check should be removed.
>
> [2]
> https://dpdk.org/ml/archives/dev/2018-March/093489.
> htmlhttps://dpdk.org/ml/archives/dev/2018-March/093489.html
>
> <...>
>
> > + dev_conf = &dev->data->dev_conf;
> > + rxmode = &dev_conf->rxmode;
> > +
> > + if (rx_conf->offloads != rxmode->offloads) {
> > + RTE_LOG(ERR, PMD, "queue %u rx offloads not as port
> offloads\n",
> > + queue_idx);
> > + RTE_LOG(ERR, PMD, "\tport: %" PRIx64 "\n",
> rxmode->offloads);
> > + RTE_LOG(ERR, PMD, "\tqueue: %" PRIx64 "\n",
> rx_conf->offloads);
> > + return -EINVAL;
> > + }
>
> The offload API is changing [1], this check is no more valid. If PMD is not
> supporting queue specific offload app will not send port offloads here.
>
> [1]
> https://dpdk.org/ml/archives/dev/2018-March/092978.html
>
> <...>
>
> > + dev_conf = &dev->data->dev_conf;
> > + txmode = &dev_conf->txmode;
> > +
> > + if (tx_conf->offloads != txmode->offloads) {
> > + RTE_LOG(ERR, PMD, "queue %u tx offloads not as port
> offloads",
> > + queue_idx);
> > + return -EINVAL;
> > + }
> > +
>
> Same as above.
>
Thank you for the review.
I will remove those checks and send a new path version.
next prev parent reply other threads:[~2018-03-31 16:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 14:30 Alejandro Lucero
2018-03-27 18:25 ` Ferruh Yigit
2018-03-31 16:53 ` Alejandro Lucero [this message]
2018-04-03 11:25 ` Ferruh Yigit
2018-04-06 14:59 ` Ferruh Yigit
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=CAD+H990MftyWwLSCzfK07PzwsgY1rSA+5JdSPGDKywHbNBP3HQ@mail.gmail.com \
--to=alejandro.lucero@netronome.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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).