Messages in this thread | | | Date | Fri, 9 Nov 2001 10:39:59 -0700 | From | Richard Gooch <> | Subject | Re: Scheduling of low-priority background processes |
| |
Pavel Machek writes: > Hi! > > I foolishly muttered: > > > > > What if the SCHED_IDLE behaviour only applies when the process > > > is in userspace? Couldn't scheduler compare the process's > > > instruction pointer against the kernel/user break point, and > > > if the process is in the kernel, then just treat it like a > > > normal process? > > > > ...eek. I clearly wasn't thinking straight with that one. There > > isn't a (non-disgusting) way of determining in the scheduler if a > > process is executing a syscall apart from sys_sched_yield, is there. > > Actually, something similar was implemented. New process flag was > added, and when process did syscall, it lost SCHED_IDLE flag, and it > was returned to it when it went back to userland.
That's the sensible approach. Is anyone maintaining that patch and sending it to Linus for inclusion?
Regards,
Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |