On Wed, Jul 23, 2008 at 5:15 PM, Scott Lovenberg <[EMAIL PROTECTED]> wrote: > Peter Teoh wrote: > > > I believe it may also happen if a new process with a high priority enters > the run queue and in order to malloc() RAM for it, a soon to be run or just > run process of a lower priority has to be swapped out from the run queue. > I'm just guessing, but IIRC, most *NIX schedulers will swap out a runnable > task if a new higher priority task enters the system and needs the memory. > That leaves it in a ready/runnable state while 'on ice' so far as its memory > pages go. Please correct me if I'm wrong, it's 5AM here :) > >
Yes I think your case scenario sounds logical enough. -- Regards, Peter Teoh -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to [EMAIL PROTECTED] Please read the FAQ at http://kernelnewbies.org/FAQ
