On Fri, Jan 05, 2007 at 02:14:26PM +0000, Robert Watson wrote: > > On Fri, 5 Jan 2007, lulf_at_stud.ntnu.no wrote: > > > Anyway, I'd like to research a bit on this topic to just see how much it > > does matter with different I/O scheduling for different purposes. > > I think working on this is interesting, but the one caution I'd have is that > it's possibly to introduce serious priority inversions through any complex > scheduling scheme for I/O. In our VFS, I/O is frequently performed while > holding locks or things that act like locks -- for example, during a directory > lookup, while pulling an inode off the disk, etc. The I/O will be initiated > by one thread, but then other threads will end up waiting for it also. If > there is a naive mapping of initiating thread priority to I/O request > priority, then you can end up with high priority threads being blocked on a > low priority tasks, leading to nasty starvation effects, especially if the > scheduler allows indefinite waiting for I/O at a low priority. This, at a that's a problem with priority based schedulers. neither the elevator nor the proportional-fair scheduler in Hybrid, nor a plain FIFO scheduler soffer from this 'indefinite waiting' problem. If i remember well the elevator code in freebsd had some support for 'prioritized' requests that could go in front of the queue no matter what, but i think that part was not really used. cheers luigiReceived on Fri Jan 05 2007 - 17:46:57 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:04 UTC