From: Andreas Hasenack <andreas@conectiva.com.br>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] many ways to do load balancing (or not?)
Date: Thu, 21 Nov 2002 19:11:23 +0000 [thread overview]
Message-ID: <marc-lartc-103790596612352@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103788125614081@msgid-missing>
Em Thu, Nov 21, 2002 at 12:46:56PM -0500, Ashok N N escreveu:
> i believe that SNAT is for connections initiated from outside world towards
> the internal network. and this would be reverse of what is intended here,
That's DNAT.
> i'm still looking at the code here. AFAIK, the when you have multipath option
> set, then when looking up for a route to an address, among the multiple equal
> cost paths, one is selected according to some criteria (i read random
> somewhere in the kernel but am not able to locate it now). but once the route
This criteria I would like to understand.
> route. so it is kind of a route-based load-balancing.
Considering that the route cache is 60s by default, this should work I guess.
I'm setting up such a setup for testing.
> i read in one of the threads that 'equalize' causes per-packet load balancing,
> i.e looks up the route for each packet. but i am doubtful about the
> performance when each packet causes a route-lookup in the FIB.
> (http://www.uwsg.iu.edu/hypermail/linux/net/0107.3/0028.html)
Interesting, so 'equalize' bypasses the cache, that's about it?
So we only need to know the criteria with which the route is choosed in a multipath
route. Packet count? Round robin?
> > d) OSPF. I read in the RFC that OSPF can do "load balancing", but I failed
> > to understand how (no, I didn't read that RFC thoroughly, it's really high
> > tech for me at this point). Does it use multipath routes to accomplish this?
Any thoughts on how OSPF does this?
Thanks for your input
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-11-21 19:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-21 12:19 [LARTC] many ways to do load balancing (or not?) Andreas Hasenack
2002-11-21 17:46 ` Ashok N N
2002-11-21 19:11 ` Andreas Hasenack [this message]
2002-11-21 20:00 ` Ramin Alidousti
2002-11-21 22:20 ` William L. Thomson Jr.
2002-11-21 22:55 ` Christoph Simon
2002-11-21 23:41 ` Christoph Simon
2002-11-22 0:06 ` William L. Thomson Jr.
2002-11-22 0:24 ` William L. Thomson Jr.
2002-11-22 1:17 ` Ashok N N
2002-11-22 12:28 ` Andreas Hasenack
2002-11-22 12:30 ` Andreas Hasenack
2002-11-22 12:39 ` Andreas Hasenack
2002-11-22 12:41 ` Andreas Hasenack
2002-11-22 13:00 ` Christoph Simon
2002-11-22 13:26 ` Vincent Jaussaud
2002-11-22 18:05 ` William L. Thomson Jr.
2002-11-22 18:21 ` William L. Thomson Jr.
2002-11-22 18:37 ` William L. Thomson Jr.
2002-11-22 18:47 ` William L. Thomson Jr.
2002-11-22 20:34 ` Andreas Hasenack
2002-11-25 13:20 ` Vincent Jaussaud
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=marc-lartc-103790596612352@msgid-missing \
--to=andreas@conectiva.com.br \
--cc=lartc@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