Subject: VM_NOSLEEP on vmlocking branch (Re: CVS commit: [vmlocking] src/sys)
To: None <ad@netbsd.org>
From: YAMAMOTO Takashi <yamt@mwd.biglobe.ne.jp>
List: tech-kern
Date: 03/14/2007 08:16:33
> Module Name:	src
> Committed By:	ad
> Date:		Tue Mar 13 17:51:59 UTC 2007
> 
> Modified Files:

> 	src/sys/fs/smbfs [vmlocking]: smbfs_vfsops.c
> 	src/sys/kern [vmlocking]: exec_subr.c init_main.c kern_exit.c
> 	    kern_lock.c kern_lwp.c kern_mutex.c kern_physio.c kern_sig.c
> 	    kern_subr.c kern_synch.c subr_extent.c subr_pool.c
> 	    subr_specificdata.c subr_vmem.c sys_process.c sys_sig.c
> 	    syscalls.master vfs_bio.c vfs_lockf.c vfs_subr.c vfs_syscalls.c
> 	    vfs_vnops.c

> Log Message:
> Pull in the initial set of changes for the vmlocking branch.

my understanding of VM_NOSLEEP for vmem_create is that
it merely means vmem_create itself shouldn't sleep.

i think you need to change the api or make everything which can
use vmem interrupt threads.

YAMAMOTO Takashi