> You will *probably* get stable 16GB with the vendor tuned enterprise
> kernels (RHEL, CentOS etc),
That's sounds "a little" relief. Thesis 1,2,3 has 16GB memory. Aries has 12G.
Tony Wang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EM
(removing Alan Cox from the Cc: list; He does not need to be involved
in the details of our discussions of local systems ...)
On Mon, 17 Dec 2007 [EMAIL PROTECTED] wrote:
> ... Thesis 1,2,3 has 16GB memory. Aries has 12G.
Note that the Theses and Aries are Xeon systems, which are 32-bit system
On Mon, 17 Dec 2007 10:44:05 -0500 (EST)
[EMAIL PROTECTED] wrote:
> > You will *probably* get stable 16GB with the vendor tuned enterprise
> > kernels (RHEL, CentOS etc),
>
> That's sounds "a little" relief. Thesis 1,2,3 has 16GB memory. Aries has 12G.
If you can run a 64bit kernel, it will save
> ...but I've run into a situation in which a system on which I *have* set
> no overcommit is being blasted by the OOM killer anyway.
Looks like the kernel is eating all the resources needed.
>Linux babyalcor 2.6.23.1 #1 SMP Fri Oct 26 15:35:18 EDT 2007 \
> i686 Dual Core AMD Opteron(tm)
On Fri, 07 Dec 2007 10:25:23 +0100
Martin MOKREJŠ <[EMAIL PROTECTED]> wrote:
> Hi,
> first of all, sorry for not being up to date with how the OOM killer
> works. I think there used to be a kernel config option to disable
> OOM killer and instead kill the process which actually asks for the
> me
Marting Mokreja wrote:
> first of all, sorry for not being up to date with how the OOM killer
> works. I think there used to be a kernel config option to disable
> OOM killer and instead kill the process which actually asks for the
> memory and supposedly caused the memory lack. That is what I woul
6 matches
Mail list logo
