DPDK patches and discussions
 help / color / mirror / Atom feed
From: Sunil Kumar Kori <sunil.kori@nxp.com>
To: <dev@dpdk.org>
Cc: <sunil.kori@nxp.com>, <hemant.agrawal@nxp.com>
Subject: [dpdk-dev] [PATCH v2 0/2] Non-supported offloads are ignored
Date: Mon, 23 Apr 2018 18:03:35 +0530	[thread overview]
Message-ID: <20180423123337.5653-1-sunil.kori@nxp.com> (raw)
In-Reply-To: <20180420104541.21987-1-sunil.kori@nxp.com>

Currently DPAA/DPAA2 driver returns error if non-supported offloads
(Rx or Tx) are requested from user which causes init failures in
multiple application.

Some offloads may be enabled by default in many hardware and cannot
be disabled. These offloads cannot be part of capability as toggling
is not allowed (Like CRC STRIP). Thus DPAA/DPAA2 driver will ignore
such offloads and rather print warning message.

Change History:
[v2] Incorporated review comments

Sunil Kumar Kori (2):
  net/dpaa: non supported offloads are ignored with warning
  net/dpaa2: non supported offloads are ignored with warning

 drivers/net/dpaa/dpaa_ethdev.c   | 34 +++++++++++++++++++++++++++-------
 drivers/net/dpaa2/dpaa2_ethdev.c | 37 +++++++++++++++++++++++++++++--------
 2 files changed, 56 insertions(+), 15 deletions(-)

-- 
2.9.3

  parent reply	other threads:[~2018-04-23 12:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-20 10:45 [dpdk-dev] [PATCH " Sunil Kumar Kori
2018-04-20 10:45 ` [dpdk-dev] [PATCH 1/2] net/dpaa: non supported offloads are ignored with warning Sunil Kumar Kori
2018-04-20 15:20   ` Stephen Hemminger
2018-04-20 10:45 ` [dpdk-dev] [PATCH 2/2] net/dpaa2: " Sunil Kumar Kori
2018-04-20 12:27 ` [dpdk-dev] [PATCH 0/2] Non-supported offloads are ignored Ferruh Yigit
2018-04-23 12:33 ` Sunil Kumar Kori [this message]
2018-04-23 12:33   ` [dpdk-dev] [PATCH v2 1/2] net/dpaa: non supported offloads are ignored with warning Sunil Kumar Kori
2018-04-23 14:57     ` Ferruh Yigit
2018-04-23 12:33   ` [dpdk-dev] [PATCH v2 2/2] net/dpaa2: " Sunil Kumar Kori

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=20180423123337.5653-1-sunil.kori@nxp.com \
    --to=sunil.kori@nxp.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.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).