From: Christoph Lameter <cl@linux.com>
To: Tharindu Rukshan Bamunuarachchi <btharindu@gmail.com>
Cc: Hugh Dickins <hughd@google.com>, linux-mm@kvack.org
Subject: Re: TMPFS Maximum File Size
Date: Wed, 27 Oct 2010 15:08:49 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1010271503360.6255@router.home> (raw)
In-Reply-To: <AANLkTim=6Oan-CSnGMD1CTsd5iGRr98X44TAcirQt7Q_@mail.gmail.com>
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-10-27 20:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 13:44 TMPFS Maximum File Size Tharindu Rukshan Bamunuarachchi
2010-10-20 14:14 ` Christoph Lameter
2010-10-20 16:57 ` Hugh Dickins
2010-10-26 13:55 ` Tharindu Rukshan Bamunuarachchi
2010-10-27 3:44 ` Hugh Dickins
2010-10-27 20:08 ` Christoph Lameter [this message]
2010-10-28 13:35 ` Tharindu Rukshan Bamunuarachchi
2010-10-28 13:49 ` Christoph Lameter
2010-10-29 2:01 ` Tharindu Rukshan Bamunuarachchi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.00.1010271503360.6255@router.home \
--to=cl@linux.com \
--cc=btharindu@gmail.com \
--cc=hughd@google.com \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).