DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhao, MeijuanX" <meijuanx.zhao@intel.com>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
	"Han, YingyaX" <yingyax.han@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] app/testpmd: fix dcb config failure
Date: Thu, 2 Aug 2018 02:31:24 +0000	[thread overview]
Message-ID: <9866F1E5CE768A45B24F6603C6EF54DE014147D0@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1533048214-19978-1-git-send-email-konstantin.ananyev@intel.com>



-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Konstantin Ananyev
Sent: Tuesday, July 31, 2018 10:44 PM
To: dev@dpdk.org; dev@dpdk.org
Cc: Ananyev, Konstantin <konstantin.ananyev@intel.com>
Subject: [dpdk-dev] [PATCH v2] app/testpmd: fix dcb config failure

After adding RSS hash offload check, default rss_hf will fail on devices that do not support all bits. This will lead to dcb config failure. The patch fixes this issue by reading current valid rss_conf from the device.

Fixes: 8863a1fbfc66 ("ethdev: add supported hash function check")
Fixes: 1a572499beb6 ("app/testpmd: setup DCB forwarding based on traffic class")

Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
Tested-by: Han, YingyaX <yingyax.han@intel.com>

      parent reply	other threads:[~2018-08-02  2:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-24 11:32 [dpdk-dev] [PATCH] " Xiaoyun Li
2018-07-24 16:16 ` Iremonger, Bernard
2018-07-26 17:18   ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2018-07-31 14:43 ` [dpdk-dev] [PATCH v2] " Konstantin Ananyev
2018-08-01  8:46   ` Iremonger, Bernard
2018-08-01 14:32     ` Thomas Monjalon
2018-08-02  2:31   ` Zhao, MeijuanX [this message]

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=9866F1E5CE768A45B24F6603C6EF54DE014147D0@shsmsx102.ccr.corp.intel.com \
    --to=meijuanx.zhao@intel.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    --cc=yingyax.han@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).