netdev - Re: [RFC, PATCH] IPV6 : add 64 bits components in struct in6_addr to speedup ipv6_addr_equal() & ipv6_addr

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]

Date:	Mon, 30 Apr 2007 12:10:29 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	dada1@...mosbay.com
Cc:	yoshfuji@...ux-ipv6.org, netdev@...r.kernel.org
Subject: Re: [RFC, PATCH] IPV6 : add 64 bits components in struct in6_addr
 to speedup ipv6_addr_equal() & ipv6_addr_any()

From: Eric Dumazet <dada1@...mosbay.com>
Date: Mon, 30 Apr 2007 16:28:51 +0200

> On 64bit arches, we can speedup some IPV6 addresses compares, using 64 bits fields in struct in6_addr.
> 
> I am not sure if this patch wont break some user ABI, maybe we should use some ifdef(KERNEL) ?
> 
> This patch saves some space, and also reduce number of conditional branches in ipv6_addr_equal()
> 
> # size vmlinux*
>    text    data     bss     dec     hex filename
> 6257978  692044  660472 7610494  74207e vmlinux
> 6259178  692044  660472 7611694  74252e vmlinux.before_patch
> 
> Note : Maybe ipv6_addr_cmp() could be defined on top of ipv6_addr_equal() ?
> 
> Signed-off-by: Eric Dumazet <dada1@...mosbay.com>

Unfortunately, as mentioned elsewhere, we're only able to assume
32-bit alignment of ipv6 packet headers and that isn't likely to
change any time soon.

So, for example, you patch would fill my log file with unaligned trap
messages on my sparc64 workstation.
-
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