linux-kernel - Re: [RESEND][RFC] BFQ I/O Scheduler

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 18 Apr 2008 09:44:21 +1000
From:	Aaron Carroll <aaronc@....unsw.edu.au>
To:	Avi Kivity <avi@...ranet.com>
CC:	Jens Axboe <jens.axboe@...cle.com>,
	Paolo Valente <paolo.valente@...more.it>,
	Pavel Machek <pavel@....cz>, linux-kernel@...r.kernel.org
Subject: Re: [RESEND][RFC] BFQ I/O Scheduler

Avi Kivity wrote:
> Jens Axboe wrote:
>> I was thinking about that too. Generally I've been opposed to doing
>> scheduling decisions on anything but time, since that is always
>> relevant. When to hand out slices and to what process, that algorithm is
>> really basic in CFQ and could do with an improvement.
>>   
> 
> Jumping in at random, does "process" here mean task or mms_struct?  If 
> the former, doesn't that mean that a 100-thread process can starve out a 
> single-threaded process?

task_struct.  It would also be nice to do per-user I/O scheduling..

 -- Aaron
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/