From: Patrick McHardy <kaber@trash.net>
To: Guus Sliepen <guus@warande3094.warande.uu.nl>
Cc: linux kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Updated Equalize patch
Date: Thu, 21 Mar 2002 21:54:53 +0100 [thread overview]
Message-ID: <3C9A489D.DD8993C1@trash.net> (raw)
In-Reply-To: <3C9A4270.56C09FCB@trash.net> <20020321203835.GT20420@sliepen.warande.net>
Guus Sliepen schrieb:
>
> On Thu, Mar 21, 2002 at 09:28:32PM +0100, Patrick McHardy wrote:
>
> > I've updated the equalize patch to apply on 2.4.18.
> > The patch also addresses two race conditions in
> > ip_route_input(..) and ip_route_output_key(..).
> > The rt_hash_table entry is only read locked although elements
> > from the chain can be freed if there is a matching entry with
> > RTCF_EQUALIZE set.
>
> Thank you very much! I've added it to the FTP site. I'd like to know if
> there is anything the patch does that can't be done with the bonding
> module, because otherwise I'd suggest using the latter (it's much
> cleaner and handles all Ethernet protocols).
You're welcome :)
I'm using it (better trying) to bond two ppp links together (actually
the
uplinks) without provider support by distributing the traffic according
to uplink bandwidth and spoofing source ip of link1 on link2.
I've not tried the bonding module but afaik it can't be used with ppp
links
and has to be supported by the other end so equalize looks like
the only way to do it, especially since i've got only very few high
bandwidth
connections and one link is a lot slower than the other so i can't rely
on
normal multipath routing to distribute traffic correct.
Bye,
Patrick
next prev parent reply other threads:[~2002-03-21 20:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-21 20:28 Updated Equalize patch Patrick McHardy
2002-03-21 20:38 ` Guus Sliepen
2002-03-21 20:54 ` Patrick McHardy [this message]
2002-03-21 21:05 ` Guus Sliepen
2002-03-22 16:35 ` Patrick McHardy
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=3C9A489D.DD8993C1@trash.net \
--to=kaber@trash.net \
--cc=guus@warande3094.warande.uu.nl \
--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