netdev - Re: [PATCH 00/26] IPVS: Add first IPv6 support to IPVS.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 13 Jun 2008 17:14:53 +0200
From:	Patrick McHardy <kaber@...sh.net>
To:	Julius Volz <juliusv@...gle.com>
CC:	Simon Horman <horms@...ge.net.au>, Vince Busam <vbusam@...gle.com>,
	Ben Greear <greearb@...delatech.com>,
	lvs-devel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH 00/26] IPVS: Add first IPv6 support to IPVS.

Julius Volz wrote:
> On Fri, Jun 13, 2008 at 8:26 AM, Simon Horman <horms@...ge.net.au> wrote:
>> I don't really have any concrete ideas about what a better
>> interface would look like. But I am more than happy to hash our ideas.
> 
> Good! At the moment I'm looking at various netlink docs and figuring
> out how things generally work. I think netlink probably adds a lot of
> complexity over the previous sockopt interface, but I hope it's worth
> it.
> 
> As for compatibility and extensibility, how is that best achieved with
> netlink? I've seen some examples copy whole C structs into netlink
> datagrams, but that is obviously what we don't want anymore. So the
> way to go seems to be to transfer each struct field as a separate
> netlink attribute, right?

Yes. You can also group those which belong together logically
in nested attributes.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html