From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: jamal <hadi@cyberus.ca>
Cc: netdev@oss.sgi.com, netfilter-failover@lists.netfilter.org
Subject: Re: [1/2] CARP implementation. HA master's failover.
Date: Thu, 15 Jul 2004 19:55:36 +0400 [thread overview]
Message-ID: <1089906936.6114.904.camel@uganda> (raw)
In-Reply-To: <1089905244.6114.887.camel@uganda>
[-- Attachment #1: Type: text/plain, Size: 2200 bytes --]
On Thu, 2004-07-15 at 19:27, Evgeniy Polyakov wrote:
> On Thu, 2004-07-15 at 18:44, jamal wrote:
> > Evgeniy,
> >
> > Why do you need to put this stuff in the kernel?
> > This should be implemented just the same way as VRRP was - in user
> > space.
>
> Hmm...
> Just because i think it works better being implemented in the kernel? :)
> I don't think it is a good answer thought.
>
> It is faster, it is more flexible, it has access to kernel space...
Just an addition[from private e-mail]:
> would it be possible to do load balancing at the network level with a
> userland only implementation?
>
> OpenBSD's CARP does load balancing through Source Hashing (SH), which
UCARP
> lacks support for.
Userspace can't in principle.
Current kernel implementation can't too, but it can. In principle.
But better implementation should use both carp and ct_sync and some load
balancing code, which should link ct_sync and carp.
OpenBSD has one disadvantage in this regard: it is not modular, so their
carp hooks live in if_ether.c.
In Linux we just need to use connection tracking.
ct_sync makes not exactly it but close to the idea.
> > BTW, is there a spec for this protocol or its one of those things where
> > you have to follow Yodas advice?
>
> Exactly :)
> Here are all links I found:
> http://www.countersiege.com/doc/pfsync-carp/
> http://www.openbsd.org/cgi-bin/man.cgi?query=carp&apropos=0&sektion=0&manpath=OpenBSD+Current&arch=i386&format=html#SEE+ALSO
> http://www.openbsd.org/lyrics.html
> VRRP2 spec.
> http://www.openbsd.org/cgi-bin/cvsweb/src/sys/netinet/ip_carp.c
>
>
> I do want this to be in the mainline kernel, but actually I even don't
> think anyone will apply it.
> It is too special stuff for generic kernel, it has reserved 112 vrrp
> protocol number and so on...
> So if developers decide not to include or even not to discuss this cruft
> I will not beat myself by my heels. :)
>
> It just works as expected, it is reliable and simple.
> And it does it's work, so HA people would like it.
>
> > cheers,
> > jamal
--
Evgeniy Polaykov ( s0mbre )
Crash is better than data corruption. -- Art Grabowski
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-07-15 15:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1089898303.6114.859.camel@uganda>
2004-07-15 13:36 ` [1/2] CARP implementation. HA master's failover Evgeniy Polyakov
2004-07-15 14:44 ` jamal
2004-07-15 15:27 ` Evgeniy Polyakov
2004-07-15 15:55 ` Evgeniy Polyakov [this message]
2004-07-15 16:28 ` jamal
2004-07-15 16:59 ` Evgeniy Polyakov
2004-07-15 17:30 ` jamal
2004-07-15 19:20 ` Evgeniy Polyakov
2004-07-16 12:34 ` jamal
2004-07-16 15:06 ` Evgeniy Polyakov
2004-07-17 11:52 ` jamal
2004-07-17 12:59 ` Evgeniy Polyakov
2004-07-17 15:47 ` jamal
2004-07-17 20:04 ` Evgeniy Polyakov
2004-07-15 16:07 ` jamal
2004-07-15 16:59 ` Evgeniy Polyakov
2004-07-15 17:24 ` jamal
2004-07-15 19:53 ` Evgeniy Polyakov
2004-07-16 13:04 ` jamal
2004-07-16 15:06 ` Evgeniy Polyakov
2004-07-17 12:47 ` jamal
2004-07-17 14:00 ` Evgeniy Polyakov
2004-07-17 16:29 ` jamal
2004-07-17 20:03 ` Evgeniy Polyakov
2004-07-17 20:32 ` jamal
2004-07-19 7:16 ` [nf-failover] " KOVACS Krisztian
2004-07-20 2:38 ` Harald Welte
2004-07-20 14:24 ` jamal
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=1089906936.6114.904.camel@uganda \
--to=johnpol@2ka.mipt.ru \
--cc=hadi@cyberus.ca \
--cc=netdev@oss.sgi.com \
--cc=netfilter-failover@lists.netfilter.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 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.