linux-numa.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ganapatrao Kulkarni <gpkulkarni@gmail.com>
To: linux-numa@vger.kernel.org
Subject: Re: tshared fails
Date: Mon, 22 Sep 2014 14:12:16 +0530	[thread overview]
Message-ID: <CAFpQJXVV8CD1gZfX1q2ePjG2=Xk9Qi59JAyWa5xtSVSDs9RWzQ@mail.gmail.com> (raw)
In-Reply-To: <CAFpQJXXR5quD-1wfagtao8SBDt3+SsEjVmt4t-YTqyBtPCV95w@mail.gmail.com>

On Mon, Sep 22, 2014 at 9:35 AM, Ganapatrao Kulkarni
<gpkulkarni@gmail.com> wrote:
> Hi,
>
> i am trying to run numactl test tshared on our platform for which i
> have ported numa support.
> i am trying this with kernel version 3.17
>
> the issue is numa_alloc_interleaved() fails. however same test case
> passes, if  i do below changes.
>
> 1 if i just remove fork() in the tshared.c code. then this test passes.
>
> 2. also if i just change the flag of mmap to MAP_SHARED instead  MAP_PRIVATE
> in function numa_alloc_interleaved_subset_v2, then test passes.
>
> i don't see any dependency/relation on the arch specific code that i
> have ported to this to fail.
> any idea what is going wrong? has any one tested this test on x86 with
> 3.17 kernel?
>
> i am using numactl 2.0.9
>
this test case looks to me not correct.
The VM which is set as COW are written in child process gets there own
page from respective nodes,
however Parent VM is not mapped since it is not doing any writing and
expecting the pages to be mapped from respective nodes.

> thanks
> Ganapat

      reply	other threads:[~2014-09-22  8:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-22  4:05 tshared fails Ganapatrao Kulkarni
2014-09-22  8:42 ` Ganapatrao Kulkarni [this message]

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='CAFpQJXVV8CD1gZfX1q2ePjG2=Xk9Qi59JAyWa5xtSVSDs9RWzQ@mail.gmail.com' \
    --to=gpkulkarni@gmail.com \
    --cc=linux-numa@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).