linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>,
	"Sharon, Sara" <sara.sharon@intel.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: RSS configuration in iwlwifi
Date: Wed, 20 Apr 2016 18:05:15 +0100	[thread overview]
Message-ID: <1461171915.17112.7.camel@decadent.org.uk> (raw)
In-Reply-To: <1461169379.19157.7.camel@intel.com>

[-- Attachment #1: Type: text/plain, Size: 2153 bytes --]

On Wed, 2016-04-20 at 16:22 +0000, Grumbach, Emmanuel wrote:
> On Wed, 2016-04-20 at 16:47 +0100, Ben Hutchings wrote:
> > 
> > On Wed, 2016-04-20 at 15:30 +0000, Grumbach, Emmanuel wrote:
> > > 
> > > Hi Ben,
> > > 
> > > 
> > > Thanks for looking at our code.
> > > 
> > > 
> > > On Wed, 2016-04-20 at 16:08 +0100, Ben Hutchings wrote:
> > > > 
> > > > 
> > > > I'm not sure if you were aware, but there is a standard API for
> > > > configuring RSS in network drivers, part of ethtool_ops.  I think
> > > > iwlwifi should implement that rather than a driver-specific
> > > > debugfs
> > > > interface.
> > > > 
> > > You are right, this is why Sara made this commit:
> > > 
> > > commit 854d773e4ab5869200004af4ca5d851730849903
> > > Author: Sara Sharon <sara.sharon@intel.com>
> > > Date:   Tue Mar 22 15:55:58 2016 +0200
> > > 
> > >     iwlwifi: mvm: improve RSS configuration
> > >     
> > >     Improve current RSS configuration:
> > >      * Use netdev_rss_key instead of keeping a local copy.
> > >      * Configure also UDP hashing to have UDP traffic spread across
> > > queues.
> > >      Do not direct RSS traffic to our fallback queue.
> > > 
> > >     Signed-off-by: Sara Sharon <sara.sharon@intel.com>
> > >     Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
> > That doesn't really address what I said.  Yes, it's using the common
> > RSS key, but it's not implementing the ethtool operations to get and
> > set the indirection table and the types of flow hashing that are
> > enabled.
> > 
> Hm.. I think that setting the indirection table is a problem in our
> case because the PN check is done in the driver. The PN check is the
> way WiFi addresses the replay attack, and since the PN check relies on
> per-cpu variables, we cannot *safely* allow users to modify the
> indirection table while traffic is flowing.

I see.  You could make this work when the interface is down and return
-EBUSY if the interface is up.

Ben.

-- 
Ben Hutchings
Never attribute to conspiracy what can adequately be explained by stupidity.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2016-04-20 17:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-20 15:08 RSS configuration in iwlwifi Ben Hutchings
2016-04-20 15:30 ` Grumbach, Emmanuel
2016-04-20 15:47   ` Ben Hutchings
2016-04-20 16:22     ` Grumbach, Emmanuel
2016-04-20 16:25       ` Grumbach, Emmanuel
2016-04-20 17:05       ` Ben Hutchings [this message]
2016-04-20 19:59         ` Johannes Berg

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=1461171915.17112.7.camel@decadent.org.uk \
    --to=ben@decadent.org.uk \
    --cc=emmanuel.grumbach@intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sara.sharon@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).