From: Simon Horman <horms@verge.net.au>
To: Julius Volz <juliusv@google.com>
Cc: David Miller <davem@davemloft.net>,
csnook@redhat.com, lvs-devel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: Should we move IPVS out of net/ipv4 now?
Date: Fri, 19 Sep 2008 09:52:22 +1000 [thread overview]
Message-ID: <20080918235220.GD13536@verge.net.au> (raw)
In-Reply-To: <f4845fc0809181304y25e3df07xfde0f23406b519a2@mail.gmail.com>
On Thu, Sep 18, 2008 at 10:04:28PM +0200, Julius Volz wrote:
> On Wed, Sep 17, 2008 at 10:14 PM, David Miller wrote:
> > From: Chris Snook <csnook@redhat.com>
> > Date: Wed, 17 Sep 2008 14:37:33 -0400
> >
> >> Julius Volz wrote:
> >> > Since IPVS now does partial IPv6, should we finally move it from
> >> > "net/ipv4/ipvs" to "net" or to "net/netfilter"? I posted that patch a
> >> > long time ago, but that was before any of the actual v6 features, so
> >> > there was probably no interest.
> >>
> >> Whatever the netfilter people want is fine with me.
> >
> > I think, especially in the long term, putting IPVS under net/netfilter/
> > is the right thing to do.
>
> Ok thanks, I'll send the patch for that once lvs-next-2.6 or
> net-next-2.6 builds for ARCH=um again (there seems to be some breakage
> at the moment)...
Once net-next-2.6 is working again, let me know and I'll pull it
into lvs-next-2.6.
--
Simon Horman
VA Linux Systems Japan K.K., Sydney, Australia Satellite Office
H: www.vergenet.net/~horms/ W: www.valinux.co.jp/en
next prev parent reply other threads:[~2008-09-18 23:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-17 13:00 Should we move IPVS out of net/ipv4 now? Julius Volz
2008-09-17 18:37 ` Chris Snook
2008-09-17 20:14 ` David Miller
2008-09-18 20:04 ` Julius Volz
2008-09-18 23:52 ` Simon Horman [this message]
2008-09-19 0:00 ` David Miller
2008-09-19 9:47 ` Julius Volz
2008-09-19 19:45 ` David Miller
2008-09-22 9:16 ` Julius Volz
2008-09-18 4:24 ` Simon Horman
2008-09-18 20:05 ` 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=20080918235220.GD13536@verge.net.au \
--to=horms@verge.net.au \
--cc=csnook@redhat.com \
--cc=davem@davemloft.net \
--cc=juliusv@google.com \
--cc=lvs-devel@vger.kernel.org \
--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).