| 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: <20090412002527.631a5a89@lxorguk.ukuu.org.uk> Date: Sun, 12 Apr 2009 00:25:27 +0100 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: Grant Grundler <grundler@...gle.com> Cc: Linus Torvalds <torvalds@...ux-foundation.org>, Jeff Garzik <jeff@...zik.org>, Linux IDE mailing list <linux-ide@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>, Jens Axboe <jens.axboe@...cle.com>, Arjan van de Ven <arjan@...radead.org> Subject: Re: Implementing NVMHCI... > We've abstract the DMA mapping/SG list handling enough that the > block size should make no more difference than it does for the > MTU size of a network. You need to start managing groups of pages in the vm and keeping them together and writing them out together and paging them together even if one of them is dirty and the other isn't. You have to deal with cases where a process forks and the two pages are dirtied one in each but still have to be written together. Alternatively you go for read-modify-write (nasty performance hit especially for RAID or a log structured fs). Yes you can do it but it sure won't be pretty with a conventional fs. Some of the log structured file systems have no problems with this and some kinds of journalling can help but for a typical block file system it'll suck. -- 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