lkml.org 
[lkml]   [2006]   [Aug]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [patch 2/8] Implement always-locked bit ops, for memory shared with an SMP hypervisor.
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@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-08-03 03:09    [W:1.893 / U:0.072 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site