From: "David S. Miller" <davem@redhat.com>
To: shmulik.hen@intel.com
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
Date: Thu, 27 Mar 2003 08:06:27 -0800 (PST) [thread overview]
Message-ID: <20030327.080627.71980411.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0303271705580.7106-100000@jrslxjul4.npdj.intel.com>
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?
prev parent reply other threads:[~2003-03-27 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-27 15:38 [Bonding][patch] Adding Transmit load balancing mode to bonding shmulik.hen
2003-03-27 16:06 ` David S. Miller [this message]
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=20030327.080627.71980411.davem@redhat.com \
--to=davem@redhat.com \
--cc=bonding-announce@lists.sourceforge.net \
--cc=bonding-devel@lists.sourceforge.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=shmulik.hen@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).