linux-numa.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Max Laier" <max@laiers.net>
To: Andi Kleen <andi@firstfloor.org>
Cc: Christoph Lameter <cl@linux-foundation.org>,
	Max Laier <max@laiers.net>,
	linux-numa@vger.kernel.org, David Rientjes <rientjes@google.com>
Subject: Re: alloc_pages_node(... GFP_KERNEL | GFP_THISNODE ...) fails
Date: Fri, 29 May 2009 18:18:44 +0200	[thread overview]
Message-ID: <77c923d17135ad7a3be01d4661b51210.squirrel@mlaier.homeunix.org> (raw)
In-Reply-To: <20090529150157.GT1065@one.firstfloor.org>


Am Fr, 29.05.2009, 17:01, schrieb Andi Kleen:
> On Fri, May 29, 2009 at 09:54:06AM -0400, Christoph Lameter wrote:
>> On Fri, 29 May 2009, Max Laier wrote:
>>
>> > Same result.  "numa_hit" in node 7 increases, while "nr_free_pages"
>> stays
>> > the same.  Anything else you'd want me to watch out for?
>>
>> That looks like a bug in fake numa.
>
> I also got some reports of fake numa being a bit broken recently.

That might have been me too - I sent you a private mail earlier this week.

I guess the question is, what is special about my allocation in KVM as
opposed to the allocation in the test module (that works as expected). 
The userland test tools from the numactl package also work as expected in
membind mode.

Also, I have been reading the fake numa setup back and forth and I really
don't see any obvious difference to the ACPI driven setup - so maybe it's
a general problem, but it's just that more people are running fake numa so
the problem is reported there first?

I'll take another look at the fake numa setup later today.  Any chance
somebody could give the KVM thing a try on real numa hardware?  Though
there are probably not that many systems that have real numa and kvm
support ... dual socket Gainestown setup anyone?

-- 
/"\  Best regards,                      | mlaier@freebsd.org
\ /  Max Laier                          | ICQ #67774661
 X   http://pf4freebsd.love2party.net/  | mlaier@EFnet
/ \  ASCII Ribbon Campaign              | Against HTML Mail and News

  reply	other threads:[~2009-05-29 16:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-29  0:30 alloc_pages_node(... GFP_KERNEL | GFP_THISNODE ...) fails Max Laier
     [not found] ` <f568093c0905281743i63e1a24ak681df87bc83826ce@mail.gmail.com>
2009-05-29  0:46   ` Christoph Lameter
2009-05-29  1:09     ` Max Laier
2009-05-29 13:54       ` Christoph Lameter
2009-05-29 15:01         ` Andi Kleen
2009-05-29 16:18           ` Max Laier [this message]
2009-05-29 16:36             ` Andi Kleen
2009-05-29 16:45               ` Max Laier
2009-05-29 18:26                 ` Andi Kleen
2009-05-29 20:39                   ` Max Laier
2009-06-02 20:13                     ` Andi Kleen
2009-06-02 22:59                     ` David Rientjes
2009-06-03 14:04                       ` Christoph Lameter
2009-06-03 18:24                         ` David Rientjes
2009-06-14  4:50                           ` Max Laier

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=77c923d17135ad7a3be01d4661b51210.squirrel@mlaier.homeunix.org \
    --to=max@laiers.net \
    --cc=andi@firstfloor.org \
    --cc=cl@linux-foundation.org \
    --cc=linux-numa@vger.kernel.org \
    --cc=rientjes@google.com \
    /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).