Messages in this thread | | | Subject | Re: 2.5.59-mm5 | Date | Fri, 24 Jan 2003 08:59:37 -0800 | From | "Luck, Tony" <> |
| |
Andrew Morton wrote:
So what anticipatory scheduling does is very simple: if an application has performed a read, do *nothing at all* for a few milliseconds. Just return to userspace (or to the filesystem) in the expectation that the application or filesystem will quickly submit another read which is closeby.
Do you need to give a process being woken from the read an extra priority boost to make sure that it actually gets run in your "few milliseconds" window. It would be a shame to leave the disk idle for the interval, and then discover that the process scheduler had been running other stuff, so that the reader didn't get a chance to issue the next read.
-Tony Luck
- 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/
| |