To read all comments associated with this story, please click here.
This is why there is BLK-MTD for linux. SSD drives are flash drive at the core with a layer on top of it making the system think it is a block device. However, it does not have the same performance as a SATA disk, but that of a flash drive. BLK-MTD is a layer on top of the block device making a block device appear as MTD. You can use jffs2 on BLK-MTD on a SSD, or UBIFS, or LogFS.
Fine !
Thats been profound :-)
So, why did noone else talk about the
necessity of block2mtd ?
Isn't that overhead compared to the SSDs onboard
drive logic ?
Oh, Wikipedia tells me Aspire Ones are
equipped e.g. with an Intel® Z-P230 SSD.
And Intel says in the Preliminary Product Manual :
The PATA controller in the Intel® Z-P230 PATA Solid State Drive uses
a microcontrollerbased architecture that enables two flash memory
channels to service read and write operations. See Figure 3,
“Functional Block Diagram of Intel Z-P230 PATA Solid State Drive”
on page 7. Capable of performing flash management functions, the
SSD also implements internal wear leveling to
minimize system overhead.
Now, that even enables Windows to be installed on those
- without tweaking device type emulation layers and experimental filesystems.
Carry on ...
Edited 2008-09-09 16:50 UTC





Member since:
2007-09-08
Hello fanboys,
what 'bout a bit of recherche ?
A SSD is different from a pure piece
of flash memory. Its an advanced controller
presenting multiple parts of flash memory as
a SATA disk to bus hardware and OS. It handles
multi-channel access and wear-leveling internally.
(fine specimen even include a DRAM buffer).
Shooting at it with jffs, logfs, FATxy or
whatsoever will never hit a distinct flash
memory cell.
(btw, would youve expected Sandisk and others
asking microsoft about a Vista release with
an especially created filesystem for their
upcoming high capacity SSDs ?)
Anyone out there with profund informations about
an actual filesystem derivate that take care
of real SSD features ?
Bye