summaryrefslogtreecommitdiffstats
path: root/kernel/rcu
diff options
context:
space:
mode:
authorPaul E. McKenney <paulmck@linux.vnet.ibm.com>2016-08-09 21:15:15 -0700
committerPaul E. McKenney <paulmck@linux.vnet.ibm.com>2016-08-22 09:25:33 -0700
commited2bec07fd1aa47f1c06be92c164c13c70fb7a45 (patch)
tree42c5a07deb9a7f984b9c6631e86d60dabcdedb68 /kernel/rcu
parente1ef69217f68b8407245e9e353cf88cc2f9ebc18 (diff)
downloadop-kernel-dev-ed2bec07fd1aa47f1c06be92c164c13c70fb7a45.zip
op-kernel-dev-ed2bec07fd1aa47f1c06be92c164c13c70fb7a45.tar.gz
documentation: Record reason for rcu_head two-byte alignment
There is an assertion in __call_rcu() that checks only the bottom bit of the rcu_head pointer, rather than the bottom two (as might be expected for 32-bit systems) or the bottom three (as might be expected for 64-bit systems). This choice might be a bit surprising in these days of ubiquitous 32-bit and 64-bit systems. This commit therefore records the reason for this odd alignment check, namely that m68k guarantees only two-byte alignment despite being a 32-bit architectures. Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Diffstat (limited to 'kernel/rcu')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud