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]

Message-ID: <48073F15.7070502@cse.unsw.edu.au>
Date:	Thu, 17 Apr 2008 22:14:13 +1000
From:	Aaron Carroll <aaronc@....unsw.edu.au>
To:	Fabio Checconi <fchecconi@...il.com>
CC:	Paolo Valente <paolo.valente@...more.it>,
	Jens Axboe <jens.axboe@...cle.com>,
	Pavel Machek <pavel@....cz>, linux-kernel@...r.kernel.org
Subject: Re: [RESEND][RFC] BFQ I/O Scheduler

Fabio Checconi wrote:
>> From: Aaron Carroll <aaronc@....unsw.edu.au>
>> How do you figure that?  This is a situation where time-slices work nicely,
>> because they implicitly account for the performance penalty of poor access
>> patterns.  The sequential-accessing processes (and the system overall) ends
>> up with higher throughput.
>>
> 
> The unfairness is not WRT tasks generating poor access patterns.
> If you have two tasks doing sequential accesses on two different
> regions of the disk the exact amount of service they receive in the
> same amount of time depends on the transfer rate of the disk on
> that regions, and, depending on the media, it is not always the same.

Ok... you're talking about ZBR.

I'm not convinced this should be treated differently to, say, random vs.
sequential workloads.  You still end up with reduced global throughput as
you've shown in the ``Short-term time guarantees'' table.  It is an
interesting case though... since the lower performance is not though fault
of the process it doesn't seem fair to ``punish'' it.

 -- 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/