| 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
| ||
|
Message-ID: <20100626115632.GA31209@lst.de> Date: Sat, 26 Jun 2010 13:56:32 +0200 From: Christoph Hellwig <hch@....de> To: Jens Axboe <jaxboe@...ionio.com> Cc: Vivek Goyal <vgoyal@...hat.com>, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, czoccolo@...il.com Subject: Re: trying to understand READ_META, READ_SYNC, WRITE_SYNC & co On Sat, Jun 26, 2010 at 01:20:55PM +0200, Jens Axboe wrote: > The whole idling/anticipation is all about knowing when to > stall the queue very briefly for sync io, allowing that single > sync stream to make good progress for a while before switching > to something else. This switching back and forth potentially > destroyes throughput for the O_DIRECT writer, especially for > disks with write through caching. > > Christoph, you seem not to agree on the concept of idling. I'm still trying to understand the use case. Basically CFQ gets worse results for any workload I'm looking at, be that from the filesystem developer point of view, or virtualization point of view. And it tends to get worse the more intelligence is added to CFQ. If we could actually narrow down what it's supposed to help with into useful benchmarks that can be trivially reproduced a lot of things would be easier. -- 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/
Powered by blists - more mailing lists