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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 4 Dec 2007 13:54:21 -0800 From: "Jared Hulbert" <jaredeh@...il.com> To: "Alan Cox" <alan@...rguk.ukuu.org.uk> Cc: "Chris Friesen" <cfriesen@...tel.com>, linux-kernel@...r.kernel.org Subject: Re: solid state drive access and context switching > > microseconds level and an order of magnitude higher bandwidth than > > SATA. Is that fast enough to warrant this more synchronous IO? > > See the mtd layer. Right. The trend is to hide the nastiness of NAND technology changes behind controllers. In general I think this is a good thing. Basically the changes in ECC and reliability change very rapidly in this technology. Having custom controller hardware to handle this is faster than handling it in software and makes for a nice modular interface. We don't rewrite our SATA drivers and filesystem everything the magnetic media switches to a new recording scheme, we just plug it in. SSD's are going to be like that even if they aren't SATA. However, the MTD layer is more about managing the chips themselves, which is what the controllers are for. Maybe I'm missing something but I don't see it. We want a block interface for these devices, we just need a faster slimmer interface. Maybe a new mtdblock interface that doesn't do erase would be the place for? > > BTW - This trend toward faster, lower latency busses is marching > > forward. 2 examples; the ioDrive from Fusion IO, Micron's RAM-module > > like SSD concept. > > Very much so but we can do quite a bit in 10,000 processor cycles ... > > Alan > -- 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