netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Julius Volz" <juliusv@google.com>
To: netdev@vger.kernel.org, lvs-devel@vger.kernel.org
Cc: "Simon Horman" <horms@verge.net.au>
Subject: [PATCH] Move IPVS from net/ipv4/ipvs to net/netfilter/ipvs in preparation for IPv6 support
Date: Fri, 4 Apr 2008 12:40:36 +0200	[thread overview]
Message-ID: <f4845fc0804040340x5e93754crcd680d26fd8982f7@mail.gmail.com> (raw)

Hi,

This patch moves IPVS from net/ipv4/ipvs to net/netfilter/ipvs, as
discussed earlier with Horms and Patrick McHardy. This is done as a
preparation for later adding IPv6 functionality to IPVS. The patch is
600kb, so I uploaded it here:

http://www-user.tu-chemnitz.de/~volz/move_ipvs_to_netfilter.patch

--------------------------
Description:
Move IPVS from net/ipv4/ipvs to net/netfilter/ipvs as a preparation
for adding IPv6 support to IPVS later on.

Signed-off-by: Julius R. Volz <juliusv@google.com>
--------------------------

It applies to the current net-2.6 tree and IPVS is working after these
changes. The patch also moves the IPVS menu options into the Netfilter
menu subtree. Please let me know if that is ok or has to be changed
(it seems ok to me, as IPVS depends on Netfilter).

Again, I'm pretty new to kernel development, so let me know of
anything that can be done better.

Thanks,
Julius Volz

-- 
Google Switzerland GmbH

             reply	other threads:[~2008-04-04 10:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-04 10:40 Julius Volz [this message]
2008-04-05  1:07 ` [PATCH] Move IPVS from net/ipv4/ipvs to net/netfilter/ipvs in preparation for IPv6 support Simon Horman
2008-04-05 10:17   ` Julius Volz
  -- strict thread matches above, loose matches on Subject: below --
2008-05-07 14:32 Julius Volz
2008-05-07 15:00 ` Joseph Mack NA3T
2008-05-07 15:51   ` Julius Volz
2008-05-09 12:49     ` Joseph Mack NA3T
2008-05-09 13:21       ` Jason Stubbs
2008-05-09 13:47         ` Julius Volz
2008-05-09 13:46       ` 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=f4845fc0804040340x5e93754crcd680d26fd8982f7@mail.gmail.com \
    --to=juliusv@google.com \
    --cc=horms@verge.net.au \
    --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).