| 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
| ||
|
Message-ID: <47DA5C8D.2020207@emc.com> Date: Fri, 14 Mar 2008 07:07:57 -0400 From: Ric Wheeler <ric@....com> To: Pavel Machek <pavel@....cz> CC: Alan Cox <alan@...rguk.ukuu.org.uk>, Benny Amorsen <benny+usenet@...rsen.dk>, linux-kernel@...r.kernel.org Subject: Re: [ANNOUNCE] Ramback: faster than a speeding bullet Pavel Machek wrote: > Hi! > >>> Everyone who has write cache turned on for their hard drives is >>> running in a mode similar to ramback anyway (except for when the file >>> system is set to force writes to the platter, but that is rare). >>> Admittedly, software crashes rarely cause the write cache to be lost, >>> but hardware failures do, practically every time. >> On the contrary - the hard disk cache is managed by the barrier logic in >> the kernel, and the ordering even on failures is fairly predictable. > > Well, not even all modern hdds support barriers... It would be really > nice to have _safe_ settings by default here... > The only really safe default is to disable the write cache by default or possibly dynamically disable the write cache when barriers are not supported by a drive. Both have a severe performance impact and I am not sure that for most casual users it is a good trade. ric -- 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