DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Mody, Rasesh" <Rasesh.Mody@cavium.com>
Cc: dev@dpdk.org, Dept-Eng DPDK Dev <Dept-EngDPDKDev@cavium.com>
Subject: Re: [dpdk-dev] [PATCH] net/qede: fix RSS table entries for 100G adapter
Date: Wed, 10 May 2017 18:13:14 +0200	[thread overview]
Message-ID: <1573572.KXZY3xMyNf@xps> (raw)
In-Reply-To: <BLUPR0701MB157290F1976C8EFC7BAE0C899FEE0@BLUPR0701MB1572.namprd07.prod.outlook.com>

08/05/2017 21:03, Mody, Rasesh:
> Hi Thomas,
> 
> > From: Rasesh Mody [mailto:rasesh.mody@cavium.com]
> > Sent: Sunday, May 07, 2017 3:53 PM
> > 
> > With the change in base APIs the logic for 100G handling needs to be
> > adjusted to pass cid values instead for queue ids. The current API works
> > assuming its queue id.
> > 
> > Fixes: 69d7ba88f1a1 ("net/qede/base: use L2-handles for RSS configuration")
> 
> This is a *CRITICAL MUST FIX* patch for 100Gb adapters supported by qed/qede on DPDK 17.05. There will be functional and performance issues/regression without this fix on 100Gb adapters. 
> 
> Without this change, RSS in 100Gb adapters do not function properly and leads to performance issues.  Rx Queue stop command on 100Gb adapter will results in FW exception, where the Rx queue stop request gets stuck in FW and leads to PMD/application error saying failed to stop RXQ 0.
> 
> The issue was introduced by one of the 17.05 base driver patches (net/qede/base: use L2-handles for RSS configuration), which has changed the logic to use queue handles instead of queue ids. However, we missed to make the corresponding changes in 17.05 QEDE for the 100Gb adapter. This patch addresses that by making changes in QEDE to work with queue handles and associate the queues to respective HW functions based on queue handles.
> 
> Please include this fix in 17.05 release.

Applied, thanks

This patch is big.
So I will wait for compilation tests of the night before releasing.

      reply	other threads:[~2017-05-10 16:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-07 22:53 Rasesh Mody
2017-05-08 19:03 ` Mody, Rasesh
2017-05-10 16:13   ` Thomas Monjalon [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=1573572.KXZY3xMyNf@xps \
    --to=thomas@monjalon.net \
    --cc=Dept-EngDPDKDev@cavium.com \
    --cc=Rasesh.Mody@cavium.com \
    --cc=dev@dpdk.org \
    /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).