Andrea Arcangeli <andrea@suse.de> writes:As a user I know it because I didn't put a kernel source into /tmp. A programm can't reasonably know that. Xen has its own memory pool and can quite agressively reclaim memory from dom0 when needed. I just ment to say that the number in /proc/meminfo can change in a second so it is not much use knowing what it said last minute. I would kill any programm that does that to find out how much free ram the system has. MfG Goswin -
| J.C. Pizarro | Re: linux+glibc memory allocator, poor performance |
| Linus Torvalds | Re: BUG: mmapfile/writev spurious zero bytes (x86_64/not i386, bisected, reproduca... |
| Greg Kroah-Hartman | [PATCH 012/196] nozomi driver |
| Vladislav Bolkhovitin | Re: [Scst-devel] Integration of SCST in the mainstream Linux kernel |
git: | |
| Peter Karlsson | RCS keyword expansion |
| Dennis Schridde | Odd number of elements in anonymous hash |
| Andreas Hildebrandt | CVS-$Id:$ replacement in git? |
| Eric Wong | Re: git-svn "cannot lock ref" error during fetch |
| Jarek Poplawski | [PATCH 00/14]: Killing qdisc->ops->requeue(). |
| jamal | [PATCH 2/3][NET_BATCH] net core use batching |
| Patrick McHardy | pkt_sched: add DRR scheduler |
| Marcel Holtmann | Bluetooth fixes for 2.6.27 |
| Charlie Clark | openbsd fail2ban |
| Richard Stallman | Real men don't attack straw men |
| Juan Miscaro | Not updating .libs-XXXXX, remember to clean it (huh?) |
| Der Engel | vlan trunking OpenBSD/Cisco switch |
