netdev - Re: [RFC 3/4] bond: support more Layer 4 protocols

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20100205084240.0bd895ab@s6510>
Date:	Fri, 5 Feb 2010 08:42:40 -0800
From:	Stephen Hemminger <shemminger@...tta.com>
To:	Patrick McHardy <kaber@...sh.net>
Cc:	David Miller <davem@...emloft.net>,
	Jay Vosburgh <fubar@...ibm.com>, netdev@...r.kernel.org,
	bonding-devel@...ts.sourceforge.net
Subject: Re: [RFC 3/4] bond: support more Layer 4 protocols

On Fri, 05 Feb 2010 11:38:05 +0100
Patrick McHardy <kaber@...sh.net> wrote:

> Stephen Hemminger wrote:
> > +/* Map of protocols with standard ports available to include in hash */
> > +static const bool has_layer4[256] = {
> > +	[IPPROTO_TCP] = 1,
> > +	[IPPROTO_UDP] = 1,
> > +	[IPPROTO_UDPLITE] = 1,
> > +	[IPPROTO_SCTP] = 1,
> > +	[IPPROTO_DCCP] = 1,
> > +	[IPPROTO_ESP] = 1,
> > +};
> > +
> 
> How about using a bitmap or u8s to keep this more compact?

I thought about that, but couldn't find a clever way to initialize at
compile time other than hardcoding constants?
--
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