From: Patrick McHardy <kaber@trash.net>
To: Julius Volz <juliusv@google.com>
Cc: netdev@vger.kernel.org
Subject: Re: Adding IPv6 support to IPVS: some general questions about kernel development
Date: Mon, 31 Mar 2008 19:47:49 +0200 [thread overview]
Message-ID: <47F123C5.70804@trash.net> (raw)
In-Reply-To: <f4845fc0803310753o56ccbae5uda1e216fa139857@mail.gmail.com>
Julius Volz wrote:
> I was redirected here from lvs-devel for a particular question. As
> part of an internship at Google, I am currently looking at porting the
> IPVS (IP virtual server) kernel part of LVS to support IPv6. First
> off, I am neither a real specialist in any of the involved areas yet
> (IPv6, load balancing) nor do I have much experience writing kernel
> code (mainly reading it for some time now), but I will try to learn as
> much as I can each day. Do expect lots of newbie questions though ;)
>
> One question I had on lvs-devel that people here might know more
> about: IPVS is currently sitting at "net/ipv4/ipvs/..." in the kernel.
> A lot of this code would probably be the same for an IPv6 version, so
> the code would have to be refactored somehow and partially moved to a
> location where it can be used by both the IPv4 and IPv6 code. Are
> there any special rules for this and what do I have to think of? For
> example, could I just move the common code to a directory "net/ipvs"
> (or even all of the code, for both IPv4 and IPv6) or would people
> object?
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.
next prev parent reply other threads:[~2008-03-31 17:47 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 [this message]
2008-03-31 18:29 ` Julius Volz
2008-04-01 5:20 ` Simon Horman
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=47F123C5.70804@trash.net \
--to=kaber@trash.net \
--cc=juliusv@google.com \
--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).