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: <1171361290.12771.77.camel@laptopd505.fenrus.org>
Date:	Tue, 13 Feb 2007 11:08:10 +0100
From:	Arjan van de Ven <arjan@...radead.org>
To:	"Martin A. Fink" <fink@....mpg.de>
Cc:	Matthias Schniedermeyer <ms@...d.de>, linux-kernel@...r.kernel.org
Subject: Re: SATA-performance: Linux vs. FreeBSD

> > 
> The problem is: FreeBSD is fast, but lacks of some special drivers. Linux has 
> all drivers but access to harddisk is unpredictable and thus unreliable!
> What can I do??


there's several tunables you can do;
1) increase /sys/block/<device>/queue/nr_requests
   the linux default is on the low side
2) investigate other elevators; cfq is great for interactive use but not
so great for max throughput. you can do this by echo'ing "deadline"
into /sys/block/<device>/scheduler
3) make sure ext3 is set to "data=writeback"; the default journalling
mode is very strict, fine for smallish files but for multi-gigabyte
it'll start to hurt
4) try to use iostat -x /dev/<foo>  1 to see what values avg-rq and
avg-qu are.. avg-rq should be at least several hundred if not more.
5) echo a larger value into /sys/block/<device>/queue/max_sectors_kb
   the default seems to be 512 which is... really low. The hw max is in
   another file in that directory; if you want max throughput set the
   max_sectors_kb value to the hw max. (you pay in terms of fairness for
   this; it's the eternal fairness/latency versus throughput tradeoff)



-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ