Re: [Discuss] Limiting amount of memory

2013-09-14 Thread Tim Callaghan
I really appreciate everyones feedback on this. I'll do some more experiments next week, what's most important to me is that I can create a box that has 8G and 16G usable, I'll just have to do reboots to find out what the correct mem= is for each. -Tim On Fri, Sep 13, 2013 at 11:50 PM, Bill

Re: [Discuss] Limiting amount of memory

2013-09-14 Thread Shankar Viswanathan
On Fri, Sep 13, 2013 at 10:10:07PM -0400, Richard Pieri wrote: Some Googling about lead me to the PCI memory hole: http://en.wikipedia.org/wiki/PCI_hole Short version: in order to boot 32-bit operating systems the BIOS or EFI firmware needs to map all PCI devices to the first 4GB of address

Re: [Discuss] Limiting amount of memory

2013-09-13 Thread Richard Pieri
Bill Bogstad wrote: On my system, they both provide identical info (If you look at the right field): Mine usually do but I recall seeing some exceptions. free does some interesting rounding if you use the -g or -m switches. -- Rich P. ___ Discuss

Re: [Discuss] Limiting amount of memory

2013-09-13 Thread Richard Pieri
Then I suspect that you have some devices using a chunk of your system RAM. For example, something like a shared RAM IGP. -- Rich P. ___ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss

Re: [Discuss] Limiting amount of memory

2013-09-13 Thread Scott Ehrlich
Dell documentation, for example, has been known to say some of its PC's hardware will eat a certain amount of RAM that you will never have access to for user space. You may want to review the docs of your system to see if it has a similar claim (m/b, video card, etc). Scott On Fri, Sep 13,

Re: [Discuss] Limiting amount of memory

2013-09-13 Thread Tim Callaghan
Ugh, this is frustrating. I asked for 8192M (8G), but ended up with 5.79G. *I booted using this section from /etc/grub.conf:* title CentOS (2.6.18-348.3.1.el5) 8G root (hd0,0) kernel /boot/vmlinuz-2.6.18-348.3.1.el5 ro root=LABEL=/ mem=8192M initrd /boot/initrd-2.6.18-348.3.1.el5.img *and here

Re: [Discuss] Limiting amount of memory

2013-09-13 Thread Bill Bogstad
On Fri, Sep 13, 2013 at 12:12 PM, Tim Callaghan tmcallag...@gmail.com wrote: Ugh, this is frustrating. I asked for 8192M (8G), but ended up with 5.79G. *I booted using this section from /etc/grub.conf:* title CentOS (2.6.18-348.3.1.el5) 8G root (hd0,0) kernel

Re: [Discuss] Limiting amount of memory

2013-09-13 Thread Richard Pieri
Bill Bogstad wrote: I think you should do a reboot, capture the output of dmesg (dmesg foo), and see what the kernel is saying about memory. No, I think Scott nailed it. I checked a couple of my Dell servers. Sure enough, the kernels report less RAM than is physically installed. -- Rich

Re: [Discuss] Limiting amount of memory

2013-09-13 Thread Richard Pieri
Bill Bogstad wrote: It would still be nice to know where the memory is being used. Some Googling about lead me to the PCI memory hole: http://en.wikipedia.org/wiki/PCI_hole Short version: in order to boot 32-bit operating systems the BIOS or EFI firmware needs to map all PCI devices to the

Re: [Discuss] Limiting amount of memory

2013-09-12 Thread Richard Pieri
Tim Callaghan wrote: What am I missing? free tells you what's available, not what's actually detected, for a variety of reasons. What you really want is the first line of /proc/meminfo. head -1 /proc/meminfo That will tell you precisely how much real, physical memory the kernel detects.

[Discuss] Limiting amount of memory

2013-09-12 Thread Tim Callaghan
I'm trying to reduce the amount of available memory on a Dell R710. It has 48GB installed, I want to be able to boot it with 8G and 16G for some of my benchmarks. I've modified my /etc/grub.conf file, copying the top section and adding to the end of the kernel line as follows: kernel

Re: [Discuss] Limiting amount of memory

2013-09-12 Thread Bill Bogstad
On Thu, Sep 12, 2013 at 7:58 PM, Richard Pieri richard.pi...@gmail.com wrote: Tim Callaghan wrote: What am I missing? free tells you what's available, not what's actually detected, for a variety of reasons. What you really want is the first line of /proc/meminfo. head -1 /proc/meminfo