Fwd: Total vs per-cpu memory



Sorry for the mistake, although otherwise clear from the context: 16GB total is
correct as there are 4GB per cpu.
francesco

--- Francesco Pietra <chiendarret@xxxxxxxxx> wrote:

Date: Thu, 31 Jan 2008 07:39:43 -0800 (PST)
From: Francesco Pietra <chiendarret@xxxxxxxxx>
Subject: Total vs per-cpu memory
To: debian64 <debian-amd64@xxxxxxxxxxxxxxxx>

This question is related to problems in running a docking computation. With
big
cases, RAM proves insufficient, resulting in immediate "segmentation fault",
so
that "top" cannot inform. Though, from the code it is clear that memory is
insufficient to rotate the object in a non-parallelized part of the program.
Smaller objects do not give problems.

My question is: with Tyan S2895 Thunder K8WE, two dual opterons and 1GB RAM
per
cpu (amd64 etch), are the 16GB available to the single cpu involved in the
computation, or are 4GB available?

Memory was set with shmmax:

kernel.shmmax = 16000000000
kernel.shmall = 16000000000

sysctl -p

Thanks
francesco pietra




____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs




____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx



Relevant Pages

  • Next July 27: boot failure(hang) on x86_64 box.
    ... Freeing unused kernel memory: 1360k freed ... ACPI: PM-Timer IO Port: 0x488 ... CPU: L2 Cache: 1024K ... # AX.25 network device drivers ...
    (Linux-Kernel)
  • Re: Re: AMD Turion ZM82: freeze with 2 cores, works with 1 core (maxcpus=1)
    ... I had a problem with memory sticks that was similar. ... Perhaps you can find a testing software for the dual core cpu from your cpu or motherboard vendor.... ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ... Trouble? ...
    (Debian-User)
  • [PATCH] Document Linuxs memory barriers [try #3]
    ... The attached patch documents the Linux kernel's memory barriers. ... I've tried to get rid of the concept of memory accesses appearing on the bus; ... barring implicit enforcement by the CPU. ...
    (Linux-Kernel)
  • Oops in 2.6.28-rc9 and -rc8 -- mtrr issues / e1000e
    ... Bios 1.04beta did show correct memory sizing in dmidecode, ... I hope this is as simple as me doing something glaringly wrong in the kernel ... DMI present. ... CPU: L2 cache: 6144K ...
    (Linux-Kernel)
  • Re: read vs. mmap (or io vs. page faults)
    ... not fit in main memory, and there are overheads related to the heuristics ... But because the CPU is underutilized, ... reasonably sized user buffer). ... You have to measure the actual overhead to see what the actual cost is. ...
    (freebsd-questions)