linux-kernel - Re: [PATCH] RCU: remove alignment padding from rcu

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:	Fri, 06 May 2011 13:13:56 +0100
From:	Richard Kennedy <richard@....demon.co.uk>
To:	Eric Dumazet <eric.dumazet@...il.com>
Cc:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	lkml <linux-kernel@...r.kernel.org>,
	Dipankar Sarma <dipankar@...ibm.com>
Subject: Re: [PATCH] RCU: remove alignment padding from rcu_data on 64 bit
 builds

On Fri, 2011-05-06 at 08:20 +0200, Eric Dumazet wrote:
...
> We could shrink this structure more, converting some 64bit fields to
> 32bit ones.
> 
> Rationale is the algo is working well on 32bit arches, no need to use
> 64bit fields.
> 
> candidates : completed, gpnum, passed_quiesc_completed, qlen,
> qlen_last_fqs_check, blimit.
> 
> Counters might be converted too.

I don't know the code well enough to make that decision ;)
Is it possible to shrink it enough to free up another cache line ?
(16 longs to ints).

CONFIG_NO_HZ adds 24 bytes so even for users with !CONFIG_NO_HZ the
variables you suggest are not enough to free a cache line.  

regards
Richard


--
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/