linux-kernel - 2.6.37 kernel poor sg(x) driver scsi hard drive performence

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]

Message-ID: <B78676C11D549249AB29226D36F4140613563537DE@WOK-SRV-020.acalsupplychain.com>
Date:	Mon, 21 Mar 2011 12:25:05 +0000
From:	Steve Allen <Steve.Allen@...lsupplychain.com>
To:	"'linux-kernel@...r.kernel.org'" <linux-kernel@...r.kernel.org>
Subject: 2.6.37 kernel poor sg(x) driver scsi hard drive performence

Hello,

My first post, apologies if asking the wrong question in the wrong place. E=
ndeavoured to be correct, read FAQ & searched mailing lists.

I have a specific use of linux as a scsi hard drive test environment. I hav=
e been using knoppix with kernel 2.6.28.4 for a number of years very sucess=
fuly.
I test 14 drives simultaneously in an external drive bay using for example =
scsi write-same erase command. Although we use a product from santools, sma=
rtmon-ux,
 sg_write_same is available form scsitools etc.

I have updated to knoppix 6.4.4 with kernel 2.6.37 and cannot test in the s=
ame manner, the performance makes the test operation impractical.
Although, I can test one drive at a time under  2.6.37 with the same test t=
ime as 2.6.28.4,   as soon as I load additional drives the test times sore =
from 18m to 134m.

I have tried googling and come across I/O throttling. Am I on the right lin=
es?
I have attempted to research cgroups but the info is mainly on limiting thr=
oughput.

Any ideas would be appreciated, happy to run any tests etc.
Many reasons why I would like to keep 2.6.37

Regards,

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