Date: Sun, 06 Mar 2005 13:49:29 +1100 From: Sam Lawrance <boris@brooknet.com.au> To: David Xu <davidxu@freebsd.org> Cc: current@freebsd.org Subject: Re: Swapped out procs not brought in immediately after child exits Message-ID: <1110077369.790.48.camel@dirk.no.domain> In-Reply-To: <422A6046.5080801@freebsd.org> References: <20050306012146.701FB17D8@localhost> <422A6046.5080801@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 2005-03-06 at 09:43 +0800, David Xu wrote: > Sam Lawrance wrote: > > >>How-To-Repeat: > >> > >> > > > >Run a shell somewhere (first). Su or run another shell or similar (second). > >Wait until the first shell has swapped out (might require running some other > >memory hogs). Exit the second shell. Notice that the second shell takes a > >long time to exit. > > > > > > > This reminds me that it is another swappable kernel stack problem, if we > don't have > it, we even needn't TDP_WAKEPROC0 hack, interesting. :) Do I understand this correctly: When a process is swapped back in, the kernel stack is faulted in immediately and user space is faulted in as needed? And without swappable kernel stack, no extra action is required because the kernel stack is already in, and user space will be faulted in as usual?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1110077369.790.48.camel>