On Mon, Feb 10, 2003 at 05:23:02PM +0100, Pavel Machek wrote:
> Hi!
>
> > The design I proposed is to have multiple I/O queues, where to apply the
> > elevator, and to choose the queue in function of the task->pid that is
> > sumbitting the bh/bio. You'll have to apply an hash to the pid and
> > you
>
> Well, if you want *fair* scheduler, as in "fair between users", I
> guess you should base it on task->uid.
Good idea. All these cases should be optional, and they make plenty of
sense to me.
> That should solve your dbench problems, too, as you are very unlikely
> to see two tasks working over same data with different uids.
yes, but the main reason we do this isn't for multiuser systems. For
multiuser systems it's true it would solve dbench, but there must be an
option to go with task->pid and being able to specify the latency
criticak tasks from userspace would be a good idea too.
Andrea
-
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/
This archive was generated by hypermail 2b29 : Sat Feb 15 2003 - 22:00:33 EST