| 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: <20080215142010.GA29552@one.firstfloor.org> Date: Fri, 15 Feb 2008 15:20:10 +0100 From: Andi Kleen <andi@...stfloor.org> To: Michael Tokarev <mjt@....msk.ru> Cc: Andi Kleen <andi@...stfloor.org>, dm-devel@...hat.com, linux-kernel@...r.kernel.org Subject: Re: [PATCH] Implement barrier support for single device DM devices On Fri, Feb 15, 2008 at 04:07:54PM +0300, Michael Tokarev wrote: > Alasdair G Kergon wrote: > > On Fri, Feb 15, 2008 at 01:08:21PM +0100, Andi Kleen wrote: > >> Implement barrier support for single device DM devices > > > > Thanks. We've got some (more-invasive) dm patches in the works that > > attempt to use flushing to emulate barriers where we can't just > > pass them down like that. > > I wonder if it's worth the effort to try to implement this. DM in theory has some more knowledge for optimization. e.g. for example if it knows that a stream of requests hits only a single device then it can just pass the barriers through again and only flush when there is really a request dependency between different devices. File systems can't do it that fine grained; it's either all or nothing. I don't know if doing it fine grained will much difference in performance though. The only way to find out would be to try it. -Andi -- 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