Re: updating COMPAT_LINUX for linux 2.6.x support (take 2)

[Matthew Mondor <mm_lists%pulsar-zone.net@localhost>]

On Thu, 17 Jun 2010 10:25:59 +0000
Andrew Doran <ad%NetBSD.org@localhost> wrote:

> This is mainly down the fact that we need kernel_lock to bracket "legacy"
> sections of code that aren't preemption safe.  I think MULTIPROCESSOR
> should be sent off to the glue factory but that's another discussion :-).

Is there any way that performance for the uniprocessor case could be
preserved, where some synchronization/preemption-safe blocks are
unnecessary, without having conditional code when MULTIPROCESSOR?

Or is it that for uniprocessor the same precautions are always required
on -current now?

Thanks,
-- 
Matt