Re: Swapped out procs not brought in immediately after child exits
From: David Xu (davidxu_at_freebsd.org)
Date: 03/06/05
- Previous message: Ivan Voras: "Mandatory Access Control"
- In reply to: Sam Lawrance: "Swapped out procs not brought in immediately after child exits"
- Next in thread: Sam Lawrance: "Re: Swapped out procs not brought in immediately after child exits"
- Reply: Sam Lawrance: "Re: Swapped out procs not brought in immediately after child exits"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 06 Mar 2005 09:43:34 +0800 To: Sam Lawrance <boris@brooknet.com.au>
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. :)
David Xu
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
- Previous message: Ivan Voras: "Mandatory Access Control"
- In reply to: Sam Lawrance: "Swapped out procs not brought in immediately after child exits"
- Next in thread: Sam Lawrance: "Re: Swapped out procs not brought in immediately after child exits"
- Reply: Sam Lawrance: "Re: Swapped out procs not brought in immediately after child exits"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|