From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail190.messagelabs.com (mail190.messagelabs.com [216.82.249.51]) by kanga.kvack.org (Postfix) with SMTP id 1ED8D6B009D for ; Wed, 27 Oct 2010 16:08:53 -0400 (EDT) Date: Wed, 27 Oct 2010 15:08:49 -0500 (CDT) From: Christoph Lameter Subject: Re: TMPFS Maximum File Size In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org To: Tharindu Rukshan Bamunuarachchi Cc: Hugh Dickins , linux-mm@kvack.org List-ID: On Tue, 26 Oct 2010, Tharindu Rukshan Bamunuarachchi wrote: > I have two node NUMA system and 100G TMPFS mount. > > 1. When "dd" running freely (without CPU affinity) all memory pages > were allocated from NODE 0 and then from NODE 1. > > 2. When "dd" running bound (using taskset) to CPU core in NODE 1 .... > All memory pages were allocated from NODE 1. > BUT machine stopped responding after exhausting NODE 1. > No memory pages were allocated from NODE 0. Hmmm... Strange it should fall back like under #1. Can you tell us where it hung? > Do you have any comment / suggestions to try out ? > Why "dd" cannot allocate memory from NODE 0 when it is running bound > to NODE 1 CPU core ? Definitely looks like a bug somewhere. TMPFS policies are not correctly falling over to more distant zones? > Core was generated by `DataWareHouseEngine Surv:1:1:DataWareHouseEngine:1'. > Program terminated with signal 11, Segmentation fault. > #0 0x00007fd924b0cf7c in write () from /lib64/libc.so.6 Hmmm... Kernel oops? Or a segfault because of an invalid reference by your app? -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org