From: Tore Anderson <tore@linpro.no>
To: Jarek Poplawski <jarkao2@o2.pl>
Cc: "David S. Miller" <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH] Improve cached ECMP documentation
Date: Wed, 07 Mar 2007 15:17:04 +0100 [thread overview]
Message-ID: <45EEC960.5000105@linpro.no> (raw)
In-Reply-To: <20070307135415.GB2268@ff.dom.local>
* Jarek Poplawski
> I don't feel bothered at all. Your letter could
> make an impression there is a lack of help and
> google not working, but it's not always true.
> So, sometimes people probably wait to see, they
> will only help and not do all your work.
Of course. I tried hard to figure it out on my own, but couldn't.
I'm sorry if I was unable to communicate that properly - I never would
ask someone for help without having attempted to figure it out on my
own first.
> Without this there is a possibility the route could be
> changed during connection.
That's no problem, it could be changed between each packet for all I
care. Connections are a TCP concept, and routers normally only care
about IPs. The routes change all the time anyway, multipath or not.
I'm quite certain I get way more than one BGP update per second in a
normal day at least.
So what I'm trying to achieve is only to better balance outgoing
traffic between two transit links to avoid saturating the physical
layer on one of the links. My multipath route achieves this nicely
when CONFIG_IP_ROUTE_MULTIPATH_CACHED is unset - thanks again! It
behaved just like a normal singlepath route when it was enabled though
(even with no multipath modules loaded) - not quite what I expected.
Regards
--
Tore Anderson
prev parent reply other threads:[~2007-03-07 14:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 20:36 Multipath routing in Linux 2.6 Tore Anderson
2007-03-07 7:39 ` Jarek Poplawski
2007-03-07 12:37 ` [PATCH] Improve cached ECMP documentation Tore Anderson
2007-03-07 13:54 ` Jarek Poplawski
2007-03-07 14:17 ` Tore Anderson [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=45EEC960.5000105@linpro.no \
--to=tore@linpro.no \
--cc=davem@davemloft.net \
--cc=jarkao2@o2.pl \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).