Date: Sat, 11 Feb 2012 14:48:47 +0100
From: Ingo Molnar <mingo@elte.hu>
To: Jesper Krogh <jesper@krogh.cc>
Cc: linux-kernel@vger.kernel.org, jk@novozymes.com,
        Andrew Morton <akpm@linux-foundation.org>,
        Yinghai Lu <yinghai@kernel.org>, Thomas Gleixner <tglx@linutronix.de>,
        "H. Peter Anvin" <hpa@zytor.com>, Tejun Heo <tj@kernel.org>,
        herrmann.der.user@googlemail.com
Subject: Re: Memory issues with Opteron 6220
Message-ID: <20120211134847.GD28098@elte.hu>
References: <20120208143741.GB28486@otto.nzcorp.net>
 <20120209083315.GA19380@elte.hu>
 <4F343582.7080007@krogh.cc>
 <4F3535E7.4000007@krogh.cc>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4F3535E7.4000007@krogh.cc>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 724
Lines: 23


* Jesper Krogh <jesper@krogh.cc> wrote:

> [...]
> 
> I would admit that we could have saved a significant of 
> time/fustration if dmesg had revealed a message that it was 
> the overcommit limits being hit and thus knocking off the 
> processes.

It would be helpful if you could enhance the printk in such a 
way, and if you tested it with your workload that triggers it - 
and send us the resulting patch. Having more information in the 
dmesg is never bad.

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/