| 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: <x49wr1cdlmg.fsf@segfault.boston.devel.redhat.com> Date: Mon, 06 Aug 2012 12:35:19 -0400 From: Jeff Moyer <jmoyer@...hat.com> To: Tatyana Brokhman <tlinder@...eaurora.org> Cc: axboe@...nel.dk, linux-mmc@...r.kernel.org, linux-arm-msm@...r.kernel.org, linux-doc@...r.kernel.org (open list:DOCUMENTATION), linux-kernel@...r.kernel.org (open list) Subject: Re: [RFC/PATCH 2/2] block: Adding ROW scheduling algorithm Tatyana Brokhman <tlinder@...eaurora.org> writes: > This patch adds the implementation of a new scheduling algorithm - ROW. > The policy of this algorithm is to prioritize READ requests over WRITE > as much as possible without starving the WRITE requests. Perhaps you could start off by describing the workload, and describing why the existing I/O schedulers do not perform well. Then, you could go on to say why you feel that the existing I/O schedulers could not be modified to perform better under your workload, and wrap the whole thing up with some convincing performance numbers (including your testing procedures so others could verify your work independently). Without the above, I think you'll have a difficult time getting yet another I/O scheduler merged into the kernel. Cheers, Jeff -- 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