linux-kernel - Re: [Scst-devel] Linux kernel and block I/O performance

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

Date:	Tue, 31 Mar 2009 21:39:32 +0400
From:	Vladislav Bolkhovitin <vst@...b.net>
To:	Bart Van Assche <bart.vanassche@...il.com>
CC:	scst-devel <scst-devel@...ts.sourceforge.net>,
	Jens Axboe <jens.axboe@...cle.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [Scst-devel] Linux kernel and block I/O performance

Hello

Bart Van Assche, on 03/25/2009 09:17 PM wrote:
> Hello,
> 
> For anyone who's running SCST performance measurements, please have a
> look at http://lwn.net/Articles/325307/. In this article it is
> explained why 2.6.25 and 2.6.29 perform three times faster on some I/O
> benchmarks than 2.6.26, 2.6.27 and 2.6.28. The relevant kernel commits
> are:
> 
> 2.6.26: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=18ce3751ccd488c78d3827e9f6bf54e6322676fb
> 2.6.29: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=78f707bfc723552e8309b7c38a8d0cc51012e813

Interesting. I've just checked with 2.6.29 on the target. With iSCSI 
still ext3 as a backstorage FS on the target a lot slower on writes than 
xfs (25-100%, deviation between runs is very high). On my system it's 
something like 50-80MB/s vs 100+MB/s. In both cases initiator formatted 
the device in ext3. Test application was famous "dd if=/dev/zero 
of=/mnt/q bs=512K".

Thanks,
Vlad
--
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/