Memory Technology Device: Difference between revisions

Content deleted Content added
added extra information
The source notes that such is a kernel interface and doesn't mention anything about OS's
 
(2 intermediate revisions by 2 users not shown)
Line 1:
{{Short description|Type of device file in Linux for interacting with flash memory}}
{{primary sources|date=December 2013}}
__NOTOC__
Line 5 ⟶ 6:
A '''Memory Technology Device''' (MTD) is a type of [[Device file system|device file]] in [[Linux]] for interacting with [[flash memory]]. The MTD subsystem was created to provide an [[abstraction layer]] between the hardware-specific device drivers and higher-level applications. Although character and block device files already existed, their semantics don't map well to the way that flash memory devices operate.
 
[[USB stick]]s, [[MultiMediaCard|MMC]]s, [[Secure Digital|SD]]s, [[CompactFlash]]es and other popular removable devices are not MTDs. Although they contain flash memory, this is hidden behind a [[block device]] interface using a [[Flash Translation Layer]] and not directly interfacing with the OSkernel.<ref>{{cite web | url=http://www.linux-mtd.infradead.org/doc/general.html#L_overview | title=Memory Technology Device Overview | accessdate=1 September 2012}}</ref>
 
When using an MTD, the use of an MTD aware file system such as [[UBIFS]], [[JFFS2]] or [[YAFFS]] is recommended. The MTD subsystem exports block devices as well, which allows the use of common filesystem like ext4. However, using an MTD this way is not recommended since there is neither detection of bad blocks nor any kind of wear leveling.
 
MTDs don't address to the OSkernel like traditional storage devices ([[Solid State Drive]], [[Hard Disk Drive]]...) using [[Logical block addressing|LBA]]s, but rather using offsets and sizes.
 
==References==