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/