Lines Matching refs:ramfs

1 ramfs, rootfs and initramfs
6 What is ramfs?
22 With ramfs, there is no backing store.  Files written into ramfs allocate
27 The amount of code required to implement ramfs is tiny, because all the
29 you're mounting the disk cache as a filesystem.  Because of this, ramfs is not
33 ramfs and ramdisk:
44 Compared to ramfs, this wastes memory (and memory bus bandwidth), creates
48 More to the point, all the work ramfs is doing has to happen _anyway_,
50 disk is simply unnecessary; ramfs is internally much simpler.
57 ramfs and tmpfs:
60 One downside of ramfs is you can keep writing data into it until you fill
62 should get written to backing store (rather than swap space), but ramfs hasn't
64 be allowed write access to a ramfs mount.
66 A ramfs derivative called tmpfs was created to add size limits, and the ability
73 Rootfs is a special instance of ramfs (or tmpfs, if that's enabled), which is
80 amount of space an empty instance of ramfs takes up is tiny.
82 If CONFIG_TMPFS is enabled, rootfs will use tmpfs instead of ramfs by
83 default.  To force ramfs, add "rootfstype=ramfs" to the kernel command