linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: roel kluin <roel.kluin@gmail.com>
To: Gary Hade <garyhade@us.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>, lkml <linux-kernel@vger.kernel.org>,
	linux-mm@kvack.org, y-goto@jp.fujitsu.com
Subject: Re: [PATCH] mm: get_nid_for_pfn() returns int
Date: Fri, 27 Feb 2009 15:56:40 +0100	[thread overview]
Message-ID: <25e057c00902270656x1781d04er5703058e47df455f@mail.gmail.com> (raw)
In-Reply-To: <20090127210727.GA9592@us.ibm.com>

>> > > get_nid_for_pfn() returns int

>> > My mistake.  Good catch.

>> Presumably the (nid < 0) case has never happened.
>
> We do know that it is happening on one system while creating
> a symlink for a memory section so it should also happen on
> the same system if unregister_mem_sect_under_nodes() were
> called to remove the same symlink.
>
> The test was actually added in response to a problem with an
> earlier version reported by Yasunori Goto where one or more
> of the leading pages of a memory section on the 2nd node of
> one of his systems was uninitialized because I believe they
> coincided with a memory hole.  The earlier version did not
> ignore uninitialized pages and determined the nid by considering
> only the 1st page of each memory section.  This caused the
> symlink to the 1st memory section on the 2nd node to be
> incorrectly created in /sys/devices/system/node/node0 instead
> of /sys/devices/system/node/node1.  The problem was fixed by
> adding the test to skip over uninitialized pages.
>
> I suspect we have not seen any reports of the non-removal
> of a symlink due to the incorrect declaration of the nid
> variable in unregister_mem_sect_under_nodes() because
>  - systems where a memory section could have an uninitialized
>    range of leading pages are probably rare.
>  - memory remove is probably not done very frequently on the
>    systems that are capable of demonstrating the problem.
>  - lingering symlink(s) that should have been removed may
>    have simply gone unnoticed.
>>
>> Should we retain the test?
>
> Yes.
>
>>
>> Is silently skipping the node in that case desirable behaviour?
>
> It actually silently skips pages (not nodes) in it's quest
> for valid nids for all the nodes that the memory section scans.
> This is definitely desirable.
>
> I hope this answers your questions.

This still isn't applied, was it lost?

Roel

--
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>

  parent reply	other threads:[~2009-02-27 14:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-18 22:36 [PATCH] mm: get_nid_for_pfn() returns int Roel Kluin
2009-01-19 17:59 ` Gary Hade
2009-01-27  6:33   ` Andrew Morton
2009-01-27 21:07     ` Gary Hade
2009-01-28  5:04       ` Yasunori Goto
2009-02-27 14:56       ` roel kluin [this message]
2009-02-27 21:33         ` Gary Hade
2009-02-27 21:46           ` Andrew Morton
2009-02-28  0:14             ` Gary Hade
2009-02-28  0:22               ` Andrew Morton
2009-02-28  3:02                 ` Gary Hade
2009-02-28  4:08                   ` Andrew Morton
2009-03-01 20:58                     ` Gary Hade

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=25e057c00902270656x1781d04er5703058e47df455f@mail.gmail.com \
    --to=roel.kluin@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=garyhade@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    --cc=y-goto@jp.fujitsu.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).