Messages in this thread | | | Date | Thu, 31 Jul 2003 15:59:37 +0100 | From | Jamie Lokier <> | Subject | Re: [PATCH] O10int for interactivity |
| |
Con Kolivas wrote: > On Thu, 31 Jul 2003 16:36, Nick Piggin wrote: > > Oh, and the process scheduler can definitely be a contributing factor. > > Even if it looks like your process is getting enough cpu, if your > > process doesn't get woken in less than 5ms after its read completes, > > then AS will give up waiting for it. > > This part interests me. It would seem that either > 1. The AS scheduler should not bother waiting at all if the process is not > going to wake up in that time
How about something as simple as: if process sleeps, and AS scheduler is waiting since last request from that process, AS scheduler stops waiting immediately?
In other words, a hook in the process scheduler when a process goes to sleep, to tell the AS scheduler to stop waiting.
Although this would not always be optimal, for many cases the point of AS is that the process is continuing to run, not sleeping, and will issue another request shortly.
-- Jamie
- 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/
| |