All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bowers, AndrewX <andrewx.bowers@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [next PATCH S61 02/10] i40e: fix configuration of	RSS table with DCB
Date: Tue, 7 Mar 2017 16:25:17 +0000	[thread overview]
Message-ID: <26D9FDECA4FBDD4AADA65D8E2FC68A4A10401EF5@ORSMSX101.amr.corp.intel.com> (raw)
In-Reply-To: <1487721348-25617-3-git-send-email-bimmy.pujari@intel.com>

> -----Original Message-----
> From: Intel-wired-lan [mailto:intel-wired-lan-bounces at lists.osuosl.org] On
> Behalf Of Bimmy Pujari
> Sent: Tuesday, February 21, 2017 3:56 PM
> To: intel-wired-lan at lists.osuosl.org
> Subject: [Intel-wired-lan] [next PATCH S61 02/10] i40e: fix configuration of
> RSS table with DCB
> 
> From: Harshitha Ramamurthy <harshitha.ramamurthy@intel.com>
> 
> There exists a bug in the driver where the calculation of the RSS size was not
> taking into account the number of traffic classes enabled. This patch factors
> in the traffic classes both in the initial configuration of the table as well as
> reconfiguration.
> 
> Signed-off-by: Harshitha Ramamurthy <harshitha.ramamurthy@intel.com>
> Change-ID: I34dcd345ce52faf1d6b9614bea28d450cfd5f621
> ---
> Testing Hints: Change the number of queues and RSS hash table via ethtool
> and ensure that no packets are dropped.
> 
>  drivers/net/ethernet/intel/i40e/i40e_main.c | 15 ++++++++++-----
>  1 file changed, 10 insertions(+), 5 deletions(-)

Tested-by: Andrew Bowers <andrewx.bowers@intel.com>



  reply	other threads:[~2017-03-07 16:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-21 23:55 [Intel-wired-lan] [next PATCH S61 00/10] i40e/i40evf updates Bimmy Pujari
2017-02-21 23:55 ` [Intel-wired-lan] [next PATCH S61 01/10] i40e/i40evf: Update code to better handle incrementing page count Bimmy Pujari
2017-03-07 16:24   ` Bowers, AndrewX
2017-02-21 23:55 ` [Intel-wired-lan] [next PATCH S61 02/10] i40e: fix configuration of RSS table with DCB Bimmy Pujari
2017-03-07 16:25   ` Bowers, AndrewX [this message]
2017-02-21 23:55 ` [Intel-wired-lan] [next PATCH S61 03/10] i40e/i40evf: Fix use after free in Rx cleanup path Bimmy Pujari
2017-03-08 18:55   ` Bowers, AndrewX
2017-02-21 23:55 ` [Intel-wired-lan] [next PATCH S61 04/10] i40e: Fixed race conditions in VF reset Bimmy Pujari
2017-03-13 14:50   ` Bowers, AndrewX
2017-02-21 23:55 ` [Intel-wired-lan] [next PATCH S61 05/10] i40e: Add support for 25G in ethtool Bimmy Pujari
2017-03-06  1:10   ` Jeff Kirsher
2017-02-21 23:55 ` [Intel-wired-lan] [next PATCH S61 06/10] i40e: fix for queue timing delays Bimmy Pujari
2017-03-07 16:29   ` Bowers, AndrewX
2017-02-21 23:55 ` [Intel-wired-lan] [next PATCH S61 07/10] i40e: removed no longer needed delays Bimmy Pujari
2017-03-07 16:30   ` Bowers, AndrewX
2017-02-21 23:55 ` [Intel-wired-lan] [next PATCH S61 08/10] i40e/i40evf: Clean-up process_skb_fields Bimmy Pujari
2017-03-07 16:30   ` Bowers, AndrewX
2017-02-21 23:55 ` [Intel-wired-lan] [next PATCH S61 09/10] i40e: Drop FCoE code from core driver files Bimmy Pujari
2017-03-07 16:31   ` Bowers, AndrewX
2017-02-21 23:55 ` [Intel-wired-lan] [next PATCH S61 10/10] i40e: Drop FCoE code that always evaluates to false or 0 Bimmy Pujari
2017-03-07 16:32   ` Bowers, AndrewX

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=26D9FDECA4FBDD4AADA65D8E2FC68A4A10401EF5@ORSMSX101.amr.corp.intel.com \
    --to=andrewx.bowers@intel.com \
    --cc=intel-wired-lan@osuosl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.