[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100720020754.135b5ff7.billfink@mindspring.com>
Date: Tue, 20 Jul 2010 02:07:54 -0400
From: Bill Fink <billfink@...dspring.com>
To: David Miller <davem@...emloft.net>
Cc: jeffrey.t.kirsher@...el.com, netdev@...r.kernel.org,
gospo@...hat.com, bphilips@...ell.com, alexander.h.duyck@...el.com,
donald.c.skidmore@...el.com
Subject: Re: [net-next-2.6 PATCH 2/5] ixgbe: drop support for UDP in RSS
hash generation
On Mon, 19 Jul 2010, David Miller wrote:
> From: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
> Date: Mon, 19 Jul 2010 16:59:27 -0700
>
> > From: Alexander Duyck <alexander.h.duyck@...el.com>
> >
> > This change removes UDP from the supported protocols for RSS hashing. The
> > reason for removing this protocol is because IP fragmentation was causing a
> > network flow to be broken into two streams, one for fragmented, and one for
> > non-fragmented and this in turn was causing out-of-order issues.
> >
> > Signed-off-by: Alexander Duyck <alexander.h.duyck@...el.com>
> > Acked-by: Don Skidmore <donald.c.skidmore@...el.com>
> > Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
>
> Applied.
Should there be a /proc or ethtool setting for whether or not to
use RSS hashing for UDP flows? I would think that for many common
UDP applications, IP fragmentation would not be an issue because
they often tend to use sub-MTU sized datagrams. And of course
UDP does not guarantee in-order delivery in any event. Then a
remaining issue is what the default setting of such an option
should be. I would lean to having it enabled by default, but
I can also see the safety argument for having it off by default.
-Bill
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists