Re: [patch 2/8] Implement always-locked bit ops, for memory sharedwith an SMP hypervisor.
From: Christoph Lameter
Date: Wed Aug 02 2006 - 21:05:09 EST
On Wed, 2 Aug 2006, Jeremy Fitzhardinge wrote:
> > Would it not be simpler to always use the locked implementation on UP? At
> > least when the kernel is compiled with hypervisor support? This is going to
> > add yet another series of bit operations
> You mean make the standard bit-ops atomic on UP when compiling for
> CONFIG_PARAVIRT? We think its too much of a burden; there are only a few
> operations which must be locked in the hypervisor case, and bit ops are used
> everywhere. I'd like to get it to the point where there's no significant
> overhead in configuring for PARAVIRT, even if you run on native hardware.
Thats a good goal but what about the rest of us who have to maintain
additional forms of bit operations for all architectures. How much is this
burden? Are locked atomic bitops really that more expensive?
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/