Re: Linux elevators (Re: BFQ: simple elevator)

2013-03-20 Thread Raymond Jennings
On Wed, Mar 20, 2013 at 4:45 PM, Arlie Stephens wrote: > On Mar 20 2013, valdis.kletni...@vt.edu wrote: >> On Wed, 20 Mar 2013 16:05:09 -0700, Arlie Stephens said: >> > The ongoing thread reminds me of a simple question I've had since I >> > first read about linux' mutiple I/O schedulers. Why is t

Re: Linux elevators (Re: BFQ: simple elevator)

2013-03-20 Thread Arlie Stephens
On Mar 20 2013, valdis.kletni...@vt.edu wrote: > On Wed, 20 Mar 2013 16:05:09 -0700, Arlie Stephens said: > > The ongoing thread reminds me of a simple question I've had since I > > first read about linux' mutiple I/O schedulers. Why is the choice of > > I/O scheduler global to the whole kernel, ra

Re: Linux elevators (Re: BFQ: simple elevator)

2013-03-20 Thread Valdis . Kletnieks
On Wed, 20 Mar 2013 16:05:09 -0700, Arlie Stephens said: > The ongoing thread reminds me of a simple question I've had since I > first read about linux' mutiple I/O schedulers. Why is the choice of > I/O scheduler global to the whole kernel, rather than per-device or > similar? They aren't global

Linux elevators (Re: BFQ: simple elevator)

2013-03-20 Thread Arlie Stephens
The ongoing thread reminds me of a simple question I've had since I first read about linux' mutiple I/O schedulers. Why is the choice of I/O scheduler global to the whole kernel, rather than per-device or similar? Consider a system with both traditional rotating disks and SSDs - not at all far fe