Re: [PATCH] keys: Discard key spinlock and use RCU for key payload
From: David Howells
Date: Wed Mar 09 2005 - 13:54:40 EST
Linus Torvalds <torvalds@xxxxxxxx> wrote:
> > The attached patch changes the key implementation in a number of ways:
> > (1) It removes the spinlock from the key structure.
> > (2) The key flags are now accessed using atomic bitops instead of
> > write-locking the key spinlock and using C bitwise operators.
> I'd suggest against using __set_bit() for the initialization. Either use
> the proper set_bit() (which is slow, but at least consistent), or just
> initialize it with (1ul << KEY_FLAG_IN_QUOTA). __set_bit is generally
> slower than setting a value (it's pretty guaranteed not to be faster, and
> at least on x86 is clearly slower), so using it as an "optimization" is
Yeah... fair enough.
> RCU seems to fit the key model pretty well, but I still wonder whether the
> conceptual complexity is worth it. Was this done on a whim, or was there
> some real reason for it?
There are two parts to the reason:
(1) Keys are for the most part invariant. Whilst they can be modified if the
type supports it, this should be uncommon. Except in the case of
keyrings, that is, but they're a special case anyway.
(2) Anything that accesses a key's payload (which includes the keyring search
algorithm) must hold the key's spinlock whilst it is looking at it, for
as long as it is looking at it.
With RCU, this is no longer necessary. You just can't schedule until
you've finished looking at it.
Given that for the most part keys don't change, it'd be very nice not to have
to get a read lock on them. For something like NFS or AFS, the key will
probably have to be accessed for every remote procedure call, for example; and
a process's keyrings will have to be searched on every open call, assuming
keys are associated with struct files or struct inodes.
The current locking model is quite complicated, and great care has to be taken
to avoid recursive deadlocks; so in some ways the RCU model is actually
> I'd love for that to be documented while you're at it..
I need to update the key documentation to reflect the changes in locking, but
the base kernel doesn't have the previous sets of doc changes; something I'd
like to build on.
When you or Andrew have released such a kernel, I'll update the docs too.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/