Differences between version 3 and revision by previous author of Tmpfs.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 3 | Last edited on Friday, October 19, 2007 12:39:01 pm | by LawrenceDoliveiro | Revert |
| Older page: | version 2 | Last edited on Monday, May 15, 2006 12:32:05 pm | by CraigBox | Revert |
@@ -1,7 +1,9 @@
-A FileSystem that uses memory to simulate a traditional disk partition
in order to offer greatly accelerated access times to its contents. In constrast to a [RamDisk] it does not simulate a block device, so it can grow and shrink as needed to accomodate the files it hosts. Together with the large amounts of RAM modern machines are typically equipped with, its impact on the memory available to other processes is nowadays often negligible. Because it does not occupy a disk [Partition], files stored on a [Tmpfs] vanish when the system shuts down.
+A FileSystem that lives entirely in the Linux filesystem cache
in order to offer greatly accelerated access times to its contents. In constrast to a [RamDisk] it does not simulate a block device, so it can grow and shrink as needed to accomodate the files it hosts. Together with the large amounts of RAM modern machines are typically equipped with, its impact on the memory available to other processes is nowadays often negligible. Because it does not occupy a disk [Partition], files stored on a [Tmpfs] vanish when the system shuts down.
Any partition that will have many, frequently accessed, small files which do not require permanent storage is a good candidate for [Tmpfs]. Of all the directories in the FileSystemHierarchy, __/tmp__ is the canonical candidate.
+
+See [this article|http://linuxdevices.com/articles/AT4017834659.html] for a more detailed explanation.
-----
CategoryFileSystem%%%
CategoryOtherFileSystem
