| 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
| ||
|
Date: Fri, 1 Apr 2011 21:39:17 +0100 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: Charles Samuels <charles@...iden.com> Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: Queuing of disk writes > I've seen this on ext3, ext4, and XFS. Reiser3 not so much. I've also > convinced my users to use write-backed cache. They're Enterprise customers and > have loads of money to spend on hardware, such as Warp Cores. ext3 certainly suffers badly from it, that is known. > > The ultima answer is probably an SSD of course 8) > Well, that would solve the throughput, but it doesn't solve the blocking! Best place to go might be linux-fsdevel - especially if you can generate a simulation of the problem workload (ie one that just does the I/O patterns) -- 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