* RE: [Bonding][patch] Adding Transmit load balancing mode to bondi ng
@ 2003-04-01 16:09 Hen, Shmulik
2003-04-01 16:58 ` David S. Miller
0 siblings, 1 reply; 2+ messages in thread
From: Hen, Shmulik @ 2003-04-01 16:09 UTC (permalink / raw)
To: David S. Miller
Cc: bonding-devel, bonding-announce, linux-net, netdev, jgarzik
We haven't experimented with layer 4 load balancing in the past. I guess
this is because of the big overhead of parsing the skb for the necessary
data, but also because of the risk of dealing with IP fragmentation, large
send issues, encryption and all kinds of off-loadings.
Shmulik.
> -----Original Message-----
> From: David S. Miller [mailto:davem@redhat.com]
> Sent: Thursday, March 27, 2003 6:06 PM
> To: Hen, Shmulik
> Cc: bonding-devel@lists.sourceforge.net;
> bonding-announce@lists.sourceforge.net;
> linux-net@vger.kernel.org; netdev@oss.sgi.com;
> linux-kernel@vger.kernel.org; jgarzik@pobox.com
> Subject: Re: [Bonding][patch] Adding Transmit load balancing
> mode to bonding
>
>
> From: shmulik.hen@intel.com
> Date: Thu, 27 Mar 2003 17:38:02 +0200 (IST)
>
> Balancing is connection oriented (e.g. by IPv4 destination address)
> so packet order is always kept.
>
> You could also key off of the destination/source port as well for
> UDP/TCP/SCTP. Have you experimented with this?
>
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Bonding][patch] Adding Transmit load balancing mode to bondi ng
2003-04-01 16:09 [Bonding][patch] Adding Transmit load balancing mode to bondi ng Hen, Shmulik
@ 2003-04-01 16:58 ` David S. Miller
0 siblings, 0 replies; 2+ messages in thread
From: David S. Miller @ 2003-04-01 16:58 UTC (permalink / raw)
To: shmulik.hen; +Cc: bonding-devel, bonding-announce, linux-net, netdev, jgarzik
From: "Hen, Shmulik" <shmulik.hen@intel.com>
Date: Tue, 1 Apr 2003 19:09:09 +0300
We haven't experimented with layer 4 load balancing in the past. I guess
this is because of the big overhead of parsing the skb for the necessary
data, but also because of the risk of dealing with IP fragmentation, large
send issues, encryption and all kinds of off-loadings.
In the modern internet, a fragmented TCP packet is nearly a bug. And
if it's encrypted, you will never see the TCP headers to begin with.
Finally, there are no "large send" issues, the TCP port information
will always be in the front of the packet.
I brought this up because it is very clear to me that various
load-balancing daemons distributed by other gigabit card vendors are
keying on the connection information in TCP packets. So someone
thinks it is worthwhile :-)
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2003-04-01 16:58 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-04-01 16:09 [Bonding][patch] Adding Transmit load balancing mode to bondi ng Hen, Shmulik
2003-04-01 16:58 ` David S. Miller
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).