linux-kernel - Re: [ANNOUNCE] DeskOpt - on fly task, i/o scheduler optimization

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] [day] [month] [year] [list]

Message-ID: <p73y7fqvxy1.fsf@bingen.suse.de>
Date:	02 Sep 2007 00:10:46 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Michal Piotrowski <michal.k.k.piotrowski@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	"CK Mailinglist" <ck@....kolivas.org>
Subject: Re: [ANNOUNCE] DeskOpt - on fly task, i/o scheduler optimization

Michal Piotrowski <michal.k.k.piotrowski@...il.com> writes:

> Here is something that might be useful for gamers and audio/video editors
> http://www.stardust.webpages.pl/files/tools/deskopt/

To make it double cool combine that with the generic genetic 
optimizer for parameters that was posted a couple of months ago.

> 
> You can easily tune CFS/CFQ scheduler params
> 
> sched_batch_wakeup_granularity_ns
> sched_latency_ns
> sched_min_granularity_ns
> sched_runtime_limit_ns
> sched_stat_granularity_ns
> sched_wakeup_granularity_ns
> 
> back_seek_max
> back_seek_penalty
> fifo_expire_async
> fifo_expire_sync
> quantum
> slice_async
> slice_async_rq
> slice_idle
> slice_sync
> 

You should probably add the device queue length too. That seems
to often have a large impact on IO scheduling because on modern
long queue controllers the Linux IO scheduler often doesn't
have much to do because the device queue just eats it all up quickly.

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