Netdev List
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Tom Herbert <therbert@google.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, chavey@google.com
Subject: Re: [PATCH] net: reset skb queue mapping when rx'ing over tunnel
Date: Sat, 25 Sep 2010 08:49:10 +0200	[thread overview]
Message-ID: <1285397350.2478.102.camel@edumazet-laptop> (raw)
In-Reply-To: <AANLkTimG9ZCZwDyo_9bYURShn7hk6ROzX4-qypo7nG5i@mail.gmail.com>

Le vendredi 24 septembre 2010 à 09:18 -0700, Tom Herbert a écrit :
> > Hmm...
> >
> > This would need to be reverted later when tunnels are updated to be
> > multiqueue aware ? I made an attempt with GRE some days ago.
> >
> > I dont understand why this patch is needed, since get_rps_cpu() has a
> > check anyway
> >
> I think the skb queue_mapping should correspond to a queue in the
> skb's device as an invariant.  In the case that an skb's device is
> change from a multiqueue device to single queue device (like GRE), the
> inconsistency in the queue_mapping is fairly innocuous, we get one
> warning but will pretty much take the unlikely branch for GRE packets
> then on.  But imagine a case where skb's device was change from one
> multiqueue device to another, but the queue mapping was not also
> updated.  This  would cause poor weighting in get_rps_cpus.  For
> example, if the new device had fewer queues than the old one,
> get_rps_cpu will bias toward using queue 0's rps mask.

I believe your patch is fine. Thanks

Acked-by: Eric Dumazet <eric.dumazet@gmail.com>



  reply	other threads:[~2010-09-25  6:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-23 21:19 [PATCH] net: reset skb queue mapping when rx'ing over tunnel Tom Herbert
2010-09-24  2:06 ` Eric Dumazet
2010-09-24 16:18   ` Tom Herbert
2010-09-25  6:49     ` Eric Dumazet [this message]
2010-09-27  1:48       ` David Miller

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=1285397350.2478.102.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=chavey@google.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=therbert@google.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