From: Simon Horman <horms@verge•net.au>
To: Ismael Luque Valencia <isma.luque@gmail•com>
Cc: Patrick McHardy <kaber@trash•net>, Michal Marek <mmarek@suse•cz>,
lvs-devel@vger•kernel.org, netdev@vger•kernel.org,
Julian Anastasov <ja@ssi•bg>,
Wensong Zhang <wensong@linux-vs•org>,
linux-kernel@vger•kernel.org
Subject: Re: IPVS scheduler algorithms (was: [PATCH] ipvs: Kconfig cleanup)
Date: Tue, 13 Jul 2010 21:29:25 +0900 [thread overview]
Message-ID: <20100713122925.GA8903@verge.net.au> (raw)
In-Reply-To: <AANLkTim3FfgxTzQ36YYYA8QG605oNW3skHZlSLKAZcjl@mail.gmail.com>
On Sun, Jul 11, 2010 at 07:15:21PM -0500, Ismael Luque Valencia wrote:
> Hi my name is Ismael, I am doing a paper about lvs algorithms but I dont
> undernstand two of them Locality-Based Least-Connection and Locality-Based
> Least-Connection with Replication
> Someone, who can explain me that algorithms please
> If it is in Spanish will better because my English is not good
Hi,
Firstly, please don't reply to emails unless you are actually
replying to the topic at hand. Instead just compose a fresh
message to the people/lists that you want to address.
This helps keep threads in mail-readers that support them sane.
In any case this question would be better sent to the lvs-users list.
But to your question.
These schedulers are described briefly in the ipvsadm(8) man page
and in pseudo code in the source files (ip_vs_lblc.c and ip_vs_lblcr.c)
in the Linux kernel tree. And there is some discussion in the howto
http://www.austintek.com/LVS/LVS-HOWTO/HOWTO/LVS-HOWTO.ipvsadm.html#DH
The way that I think of these schedulers is as enhanced versions of wlc
designed for use with transparent proxies. That is situations where
there will be a lot of destination addresses.
lblc works by keeping a cache that associates destination addresses with
a real server. This allows accesses, potentially from different end-users,
to be sent to the same real-server. As this is designed to be used
with proxies, this means the request will be sent to a proxy that may
have already retrieved the result.
lblcr is similar, but instead of one real-server per destination, it
allows for multiple real-servers per destination.
prev parent reply other threads:[~2010-07-13 12:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 20:32 [PATCH] ipvs: Kconfig cleanup Michal Marek
2010-07-04 7:05 ` Simon Horman
2010-07-04 7:13 ` Simon Horman
2010-07-05 8:43 ` Patrick McHardy
[not found] ` <AANLkTim3FfgxTzQ36YYYA8QG605oNW3skHZlSLKAZcjl@mail.gmail.com>
2010-07-13 12:29 ` Simon Horman [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=20100713122925.GA8903@verge.net.au \
--to=horms@verge$(echo .)net.au \
--cc=isma.luque@gmail$(echo .)com \
--cc=ja@ssi$(echo .)bg \
--cc=kaber@trash$(echo .)net \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=lvs-devel@vger$(echo .)kernel.org \
--cc=mmarek@suse$(echo .)cz \
--cc=netdev@vger$(echo .)kernel.org \
--cc=wensong@linux-vs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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