From: Simon Horman <horms@verge.net.au>
To: Julius Volz <juliusv@google.com>
Cc: Patrick McHardy <kaber@trash.net>, netdev@vger.kernel.org
Subject: Re: Adding IPv6 support to IPVS: some general questions about kernel development
Date: Tue, 1 Apr 2008 14:20:05 +0900 [thread overview]
Message-ID: <20080401052003.GC21127@verge.net.au> (raw)
In-Reply-To: <f4845fc0803311129w4bdb0415p56c3f11c935c3020@mail.gmail.com>
On Mon, Mar 31, 2008 at 08:29:30PM +0200, Julius Volz wrote:
> On Mon, Mar 31, 2008, Patrick McHardy <kaber@trash.net> wrote:
> > net/ipvs or net/netfilter/ipvs sound fine. The second is probably
> > better since at some point we should try to merge the duplicated
> > conntrack functionality if possible.
>
> Sure, since IPVS is basically a netfilter extension, that sounds good
> to me. Could all the IPv4- and IPv6-specific functionality (as opposed
> to the commonly used code) also end up in there or would that still
> have to reside under ipv[4,6]/...?
>
> Does it seem wise to do this move as the first thing in this process?
> That would probably be a good starter exercise to get to know the
> whole process!
I think that sounds like an excellent idea. net/netfilter/ipvs sounds
fine to me, though think that IPVS is fairly loosely tied to nefilter,
so if it was only up to me I would go for net/ipvs.
--
Horms
next prev parent reply other threads:[~2008-04-01 5:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 14:53 Adding IPv6 support to IPVS: some general questions about kernel development Julius Volz
2008-03-31 17:47 ` Patrick McHardy
2008-03-31 18:29 ` Julius Volz
2008-04-01 5:20 ` Simon Horman [this message]
2008-04-01 11:25 ` Julius Volz
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=20080401052003.GC21127@verge.net.au \
--to=horms@verge.net.au \
--cc=juliusv@google.com \
--cc=kaber@trash.net \
--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).