linux-kernel - Re: Memory issues with Opteron 6220

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 11 Feb 2012 14:48:47 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Jesper Krogh <jesper@...gh.cc>
Cc:	linux-kernel@...r.kernel.org, jk@...ozymes.com,
	Andrew Morton <akpm@...ux-foundation.org>,
	Yinghai Lu <yinghai@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>, Tejun Heo <tj@...nel.org>,
	herrmann.der.user@...glemail.com
Subject: Re: Memory issues with Opteron 6220


* Jesper Krogh <jesper@...gh.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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/