linux-kernel - [PATCH][0/2] NFS: Calculate 'w' a bit later in *_encode

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>] [day] [month] [year] [list]

Message-Id: <200611211234.00251.jesper.juhl@gmail.com>
Date:	Tue, 21 Nov 2006 12:33:59 +0100
From:	Jesper Juhl <jesper.juhl@...il.com>
To:	LKML <linux-kernel@...r.kernel.org>
Cc:	Andreas Gruenbacher <agruen@...e.de>,
	Neil Brown <neilb@....unsw.edu.au>, nfs@...ts.sourceforge.net,
	David Rientjes <rientjes@...washington.edu>,
	Andrew Morton <akpm@...l.org>,
	Jesper Juhl <jesper.juhl@...il.com>
Subject: [PATCH][0/2] NFS: Calculate 'w' a bit later in *_encode_getaclres()

Here are two patches that implement a tiny performance improvement for NFS.

The change made is to calculate the value of the 'w' variable a little 
later than is currently done. This way we don't waste time calculating 'w' 
in the cases where we return from the function before using the calculated 
value.  It also saves a few bytes of .text, which is always nice.

The last time around these got merged in -mm and subsequently dropped - 
according to akpm, they got dropped due to maintainer NACK, but my 
impression was that this change was OK.  So, this time around It would be 
great with an explicit ACK or NACK so akpm can add the patches or ignore 
them.

The two patches are send with the following subjects to the same recipients
as this mail:

  [PATCH][1/2] NFS2: Calculate 'w' a bit later in nfsaclsvc_encode_getaclres()
  [PATCH][2/2] NFS3: Calculate 'w' a bit later in nfs3svc_encode_getaclres()

Kind regards,

  Jesper Juhl <jesper.juhl@...il.com>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/