| 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: Thu, 23 Aug 2007 10:45:27 +0200 From: Jes Sorensen <jes@....com> To: James Bottomley <James.Bottomley@...senPartnership.com> Cc: Jesse Barnes <jbarnes@...tuousgeek.org>, akepner@....com, Randy Dunlap <randy.dunlap@...cle.com>, linux-kernel <linux-kernel@...r.kernel.org>, rdreier@...co.com, linux-ia64 <linux-ia64@...r.kernel.org> Subject: Re: [PATCH 2/3] dma: override "dma_flags_set_dmaflush" for sn-ia64 James Bottomley wrote: > Hmm, didn't see the email ... but I'm probably not cc'd on all the > thread. However ... it isn't that you couldn't do it ... it's that you > don't want to do it because it's faster to violate the spec ... like all > those nice ATA devices that lie about having a cache and then let you > power down with uncommitted data still in it ... they work much faster > for HDIO tests ... and who ever switches their box off? James, I didn't do it, I don't know who did it, but sure we can try and track them down and line them up outside ..... Point is that this is how the chips were done and they are out there in numbers. It makes things a *lot* faster to violate the spec in such a system, yes it sucks, but thats how things are. It wouldn't be the first time someone violated the PCI spec in their implementation and I am pretty sure it won't be the last. Cheers, Jes - 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