| 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: <20100806070424.GD2109@tux1.beaverton.ibm.com> Date: Fri, 6 Aug 2010 00:04:24 -0700 From: "Darrick J. Wong" <djwong@...ibm.com> To: "Ted Ts'o" <tytso@....edu>, Mingming Cao <cmm@...ibm.com>, Ric Wheeler <rwheeler@...hat.com>, linux-ext4 <linux-ext4@...r.kernel.org>, linux-kernel <linux-kernel@...r.kernel.org>, Keith Mannthey <kmannth@...ibm.com>, Mingming Cao <mcao@...ibm.com> Subject: Re: [RFC v2] ext4: Don't send extra barrier during fsync if there are no dirty pages. On Thu, Aug 05, 2010 at 12:45:04PM -0400, Ted Ts'o wrote: > P.S. If it wasn't clear, I'm still in favor of trying to coordinate > barriers across the whole file system, since that is much more likely > to help use cases that arise in real life. Ok. I have a rough sketch of a patch to do that, and I was going to send it out today, but the test machine caught on fire while I was hammering it with the fsync tests one last time and ... yeah. I'm fairly sure the patch didn't cause the fire, but I'll check anyway after I finish cleaning up. "[PATCH] ext4: Don't set my machine ablaze with barrier requests" :P (The patch did seem to cut barrier requests counts by about 20% though the impact on performance was pretty small.) --D -- 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