Netdev List
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Chema Gonzalez <chema@berkeley.edu>
Cc: netdev <netdev@vger.kernel.org>,
	edumazet@google.com, Chema Gonzalez <chema@google.com>
Subject: Re: [PATCH] net: Small bug on rxhash calculation
Date: Thu, 06 Sep 2012 08:42:13 +0200	[thread overview]
Message-ID: <1346913733.13121.179.camel@edumazet-glaptop> (raw)
In-Reply-To: <CAEb0MffEfboq_VmPFCtzGHe-SQ4Dd1O6Hptrc_jHVnp7itKyQg@mail.gmail.com>

On Wed, 2012-09-05 at 23:35 -0700, Chema Gonzalez wrote:
> From 5c02179069826bfba9360383b88601b31ff05517 Mon Sep 17 00:00:00 2001
> From: Chema Gonzalez <chema@google.com>
> Date: Wed, 5 Sep 2012 17:05:48 -0700
> Subject: [PATCH] net: Small bug on rxhash calculation
> 
> While the (current) sorting of the ports/addresses is coherent
> (you get the same rxhash for packets sharing the same (unsorted)
> 4-tuple), ports and addresses should not be sorted independently,
> which currently are: For traffic between A=S:l and B=L:s, packets
> in both directions would get their rxhash from hashing
> {L, S, {s, l}}. The same rxhash is obtained from packets between
> C=S:s and D=L:l.
> 
> This patch ensures traffic between A and B gets their rxhash
> from {S, L, {s, l}}, and traffic between C and D from {S, L,
> {l, s}}
> 
> The patch is co-written with Eric Dumazet <edumazet@google.com>
> 
> Signed-off-by: Chema Gonzalez <chema@google.com>
> ---

Signed-off-by: Eric Dumazet <edumazet@google.com>

Thanks !

  reply	other threads:[~2012-09-06  6:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-06  6:35 [PATCH] net: Small bug on rxhash calculation Chema Gonzalez
2012-09-06  6:42 ` Eric Dumazet [this message]
2012-09-07 16:57 ` David Miller
2012-09-07 23:40   ` [PATCH] net: small " Chema Gonzalez
2012-09-07 23:40     ` Chema Gonzalez
2012-09-07 23:50       ` David Miller
2012-09-08  0:24         ` Chema Gonzalez
2012-09-08  8:18     ` Eric Dumazet
2012-09-08 22:43       ` 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=1346913733.13121.179.camel@edumazet-glaptop \
    --to=eric.dumazet@gmail.com \
    --cc=chema@berkeley.edu \
    --cc=chema@google.com \
    --cc=edumazet@google.com \
    --cc=netdev@vger.kernel.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