[lkml]   [2006]   [Jan]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Define __raw_read_lock etc for uniprocessor builds

* Arjan van de Ven <> wrote:

> > 2) The _raw versions are intended to be used in places where it is
> > known that preemption is already disabled, so that the overhead of
> > re-disabling/enabling it can be avoided.
> that's not true either. If it was, then the name would have been
> different.

indeed. The __raw versions are _not_ to be used by anything else but the
generic spinlock code. (There's one other stray use by PARISC, but that
is justified.)

[ the -rt tree makes use of 'raw_' spinlocks, but they are totally
different things. ]

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-01-24 22:07    [W:0.029 / U:3.744 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site