On Sat, 15 Sep 2007 11:18:09 +1200 "Angus McMorland" <[EMAIL PROTECTED]> wrote: > I've made a debian live CD to allow me to perform some modelling. The > machines I have available to play with have 2 GB of RAM, which is > normally a lot more than enough to run my work. However, debian live's > tmpfs (I presume) seems to be taking up about >1 GB of that RAM,
I'm not sure if that assumption is correct. http://lxr.linux.no/source/Documentation/filesystems/tmpfs.txt tmpfs puts everything into the kernel internal caches and grows and shrinks to accommodate the files it contains and is able to swap unneeded pages out to swap space. It has maximum size limits which can be adjusted on the fly via 'mount -o remount ...' Doesn't this mean that what df reports as 'used' is all that is actually in tmpfs, and the "free" is just an upper limit (which is deceptive with multiple tmpfs mounts ... it's just showing the difference between used and the upper limit, not actual free space). But that leaves a mystery ... why is the top 1G not visible to 'free'? >From what I've read in the doc, this shouldn't happen. If I boot a small debian-live image in qemu, allocating 512M to it, 'free' tells me I have the full 512M (minus, of course, the small amount the kernel reserves for its data structures). So it looks like the kernel is not detecting the full 2G of your RAM. Ben -- ,-. nSLUG http://www.nslug.ns.ca [EMAIL PROTECTED] \`' Debian http://www.debian.org [EMAIL PROTECTED] ` [ gpg 395C F3A4 35D3 D247 1387 2D9E 5A94 F3CA 0B27 13C8 ] [ pgp 7F DA 09 4B BA 2C 0D E0 1B B1 31 ED C6 A9 39 4F ] _______________________________________________ debian-live-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/debian-live-devel
