mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Ben Greear <greearb@candelatech.com>
Cc: Andi Kleen <ak@suse.de>, Bernhard Busch <bbusch@biochem.mpg.de>,
	linux-kernel@vger.kernel.org
Subject: Re: Poor Performance for ethernet bonding
Date: Fri, 24 Aug 2001 18:04:00 +0200	[thread overview]
Message-ID: <20010824180400.B2848@gruyere.muc.suse.de> (raw)
In-Reply-To: <3B865882.24D57941@biochem.mpg.de.suse.lists.linux.kernel> <oupg0ahmv2a.fsf@pigdrop.muc.suse.de> <3B867096.3A1D7DE@candelatech.com> <20010824172256.A2531@gruyere.muc.suse.de> <3B86769D.17A979D7@candelatech.com>
In-Reply-To: <3B86769D.17A979D7@candelatech.com>; from greearb@candelatech.com on Fri, Aug 24, 2001 at 08:45:33AM -0700

On Fri, Aug 24, 2001 at 08:45:33AM -0700, Ben Greear wrote:
> On the surface, multi-path routing sounds complicated to me, while
> layer-2 bonding seems relatively trivial to set up/administer.  Since we do
> support bonding, if it's a simple fix to make it better, we
> might as well do that, eh?

multipath routing is really not complicated; I don't know why it "sounds"
complicated to you. Of course you could always add new features to the kernel
because the existing ones which do the same thing in a better way
"sound complicated" to someone; I doubt it is a good use of developer time 
however. 

BTW when you would teach bonding about flows it wouldn't be layer-2 anymore.

To kill the "sounds complicated" myth: 

ip route add 10.0.0.0/8 nexthop dev eth0 nexthop dev eth1 

gives you a multipath route with eth0 and eth1 with the same weight for 
10.0.0.0 netmask 255.0.0.0. If you replace 10.0.0.0/8 with default it'll
be your default route. The kernel does the rest.


-Andi

  reply	other threads:[~2001-08-24 16:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3B865882.24D57941@biochem.mpg.de.suse.lists.linux.kernel>
2001-08-24 13:44 ` Andi Kleen
2001-08-24 15:19   ` Ben Greear
2001-08-24 15:22     ` Andi Kleen
2001-08-24 15:45       ` Ben Greear
2001-08-24 16:04         ` Andi Kleen [this message]
2001-08-27  7:40           ` Henning P. Schmiedehausen
2001-08-24 18:17     ` Thomas Davis
2001-08-24 20:59       ` Ben Greear
2001-08-25  7:04 Willy Tarreau
2001-08-25 18:23 ` Ben Greear
2001-08-26  7:59   ` willy tarreau
  -- strict thread matches above, loose matches on Subject: below --
2001-08-24 13:37 Bernhard Busch
2001-08-24 14:12 ` Sergey Ostrovsky
2001-08-24 14:33 ` Martin Josefsson
2001-08-24 15:16   ` Ben Greear

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=20010824180400.B2848@gruyere.muc.suse.de \
    --to=ak@suse.de \
    --cc=bbusch@biochem.mpg.de \
    --cc=greearb@candelatech.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®