From: Julius Volz <juliusv@google•com>
To: netdev@vger•kernel.org, lvs-devel@vger•kernel.org
Cc: horms@verge•net.au, kaber@trash•net, davem@davemloft•net,
tgraf@suug•ch, vbusam@google•com
Subject: [PATCHv2 0/2] IPVS: Add Generic Netlink configuration interface
Date: Mon, 21 Jul 2008 15:02:53 +0200 [thread overview]
Message-ID: <1216645375-20410-1-git-send-email-juliusv@google.com> (raw)
This is the second version of the Generic Netlink interface for
IPVS. I integrated some comments from Thomas Graf, Patrick McHardy and
Yoshifuji Hideaki and changed a few things myself. The interface should
now follow existing Netlink conventions more closely and has been
tested without problems.
The two patches add a Generic Netlink interface to IPVS while keeping
the old get/setsockopt interface for userspace backwards compatibility.
The motivation for this is to have a more extensible interface for
future changes, such as the planned IPv6 support. ipvsadm is currently
being extended to support the new interface and features.
The ip_vs.h header change depends on this patch I sent previously:
"IPVS: Move userspace definitions to include/linux/ip_vs.h"
(this one looked good to Horms, can it go in?)
Julius
next reply other threads:[~2008-07-21 13:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 13:02 Julius Volz [this message]
2008-07-21 13:02 ` [PATCHv2 1/2] IPVS: Add genetlink interface definitions to ip_vs.h Julius Volz
2008-07-21 13:02 ` [PATCHv2 2/2] IPVS: Add genetlink interface implementation Julius Volz
2008-07-24 23:58 ` Thomas Graf
2008-07-25 22:39 ` Julius Volz
2008-07-22 0:34 ` [PATCHv2 0/2] IPVS: Add Generic Netlink configuration interface Simon Horman
2008-07-22 16:43 ` Julius Volz
2008-07-22 22:59 ` Vince Busam
2008-07-23 21:39 ` Vince Busam
2008-07-25 5:58 ` Simon Horman
2008-07-25 22:36 ` Julius Volz
2008-07-25 23:29 ` Thomas Graf
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=1216645375-20410-1-git-send-email-juliusv@google.com \
--to=juliusv@google$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=horms@verge$(echo .)net.au \
--cc=kaber@trash$(echo .)net \
--cc=lvs-devel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=tgraf@suug$(echo .)ch \
--cc=vbusam@google$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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