From: Patrick McHardy <kaber@trash.net>
To: Patrick Jenkins <patjenk@wam.umd.edu>
Cc: linux-kernel@vger.kernel.org, Maillist netdev <netdev@oss.sgi.com>
Subject: Re: [PATCH] multipath routing algorithm, better patch
Date: Fri, 01 Jul 2005 02:43:06 +0200 [thread overview]
Message-ID: <42C4919A.5000009@trash.net> (raw)
In-Reply-To: <Pine.GSO.4.61.0506302014160.7400@rac1.wam.umd.edu>
Patrick Jenkins wrote:
> Hi,
>
> The last patch wont work, this should.
>
> This patch assigns the multipath routing algorithm into the fib_info
> struct's fib_mp_alg variable. Previously, the algorithm was always set to
> IP_MP_ALG_NONE which was incorrect. This patch corrects the problem by
> assigning the correct value when a fib_info is initialized.
>
> This patch was tested against kernel 2.6.12.1 for all multipath routing
> algorithms (none, round robin, interface round robin, random, weighted
> random).
Multiple algorithms can be compiled in at once, so this patch is wrong.
mp_alg is supplied by userspace:
if (rta->rta_mp_alg) {
mp_alg = *rta->rta_mp_alg;
if (mp_alg < IP_MP_ALG_NONE ||
mp_alg > IP_MP_ALG_MAX)
goto err_inval;
}
If it isn't set correctly its an iproute problem. Did you actually
experience any problems?
Regards
Patrick
next prev parent reply other threads:[~2005-07-01 0:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-01 0:19 [PATCH] multipath routing algorithm, better patch Patrick Jenkins
2005-07-01 0:43 ` Patrick McHardy
2005-07-01 0:43 ` Patrick McHardy [this message]
2005-07-01 17:41 ` Thomas Graf
2005-07-01 19:34 ` Patrick McHardy
2005-07-01 20:46 ` Thomas Graf
2005-07-01 19:34 ` Patrick McHardy
2005-07-01 17:41 ` Thomas Graf
-- strict thread matches above, loose matches on Subject: below --
2005-07-05 15:17 Patrick Jenkins
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=42C4919A.5000009@trash.net \
--to=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=patjenk@wam.umd.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.