netdev - Re: [PATCH 10/14] ipv4: Use 32-bit loads for ID and length in GRO

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: <87zlcymnnf.fsf@basil.nowhere.org>
Date:	Wed, 27 May 2009 20:00:36 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Herbert Xu <herbert@...dor.apana.org.au>
Cc:	"David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org
Subject: Re: [PATCH 10/14] ipv4: Use 32-bit loads for ID and length in GRO

Herbert Xu <herbert@...dor.apana.org.au> writes:

> ipv4: Use 32-bit loads for ID and length in GRO
>
> This patch optimises the IPv4 GRO code by using 32-bit loads
> (instead of 16-bit ones) on the ID and length checks in the receive
> function.

On what architecture is that faster?

At least on x86 they should be the same performance, except that
the 16bit one is one byte larger, but that shouldn't make a difference.

-Andi

-- 
ak@...ux.intel.com -- Speaking for myself only.
--
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