linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Frank Mehnert <frank.mehnert@oracle.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: Robin Holt <holt@sgi.com>,
	linux-mm@kvack.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Hugh Dickins <hughd@google.com>
Subject: Re: Handling NUMA page migration
Date: Wed, 5 Jun 2013 03:22:32 -0700 (PDT)	[thread overview]
Message-ID: <201306051222.32786.frank.mehnert@oracle.com> (raw)
In-Reply-To: <20130605095630.GL15997@dhcp22.suse.cz>

[-- Attachment #1: Type: text/plain, Size: 2606 bytes --]

On Wednesday 05 June 2013 11:56:30 Michal Hocko wrote:
> On Wed 05-06-13 11:32:15, Frank Mehnert wrote:
> [...]
> 
> > Thank you very much for your help. As I said, this problem happens _only_
> > with NUMA_BALANCING enabled. I understand that you treat the VirtualBox
> > code as untrusted but the reason for the problem is that some assumption
> > is obviously not met: The VirtualBox code assumes that the memory it
> > allocates using case A and case B is
> > 
> >  1. always present and
> >  2. will always be backed by the same phyiscal memory
> > 
> > over the entire life time. Enabling NUMA_BALANCING seems to make this
> > assumption false. I only want to know why.
> 
> As I said earlier. Both the manual node migration and numa_fault handler
> do not migrate pages with elevated ref count (your A case) and pages
> that are not on the LRU. So if your Referenced pages might be on the LRU
> then you probably have to look into numamigrate_isolate_page and do an
> exception for PageReserved pages. But I am a bit suspicious this is the
> cause because the reclaim doesn't consider PageReserved pages either so
> they could get reclaimed. Or maybe you have handled that path in your
> kernel.

Thanks, I will also investigate into this direction.

> Or the other option is that you depend on a timing or something like
> that which doesn't hold anymore. That would be hard to debug though.
> 
> > I see, you don't believe me. I will add more code to the kernel logging
> > which pages were migrated.
> 
> Simple test for PageReserved flag in numamigrate_isolate_page should
> tell you more.
> 
> This would cover the migration part. Another potential problem could be
> that the page might get unmapped and marked for the numa fault (see
> do_numa_page). So maybe your code just assumes that the page even
> doesn't get unmapped?

Exactly, that's the assumption -- therefore all these vm_flags tricks.
If this assumption is wrong or not always true, can this requirement
(page is _never_ unmapped) be met at all?

Thanks,

Frank
-- 
Dr.-Ing. Frank Mehnert | Software Development Director, VirtualBox
ORACLE Deutschland B.V. & Co. KG | Werkstr. 24 | 71384 Weinstadt, Germany

Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRA 95603
Geschäftsführer: Jürgen Kunz

Komplementärin: ORACLE Deutschland Verwaltung B.V.
Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
Geschäftsführer: Alexander van der Ven, Astrid Kepper, Val Maher

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)

iEYEABECAAYFAlGvEWgACgkQ6z8pigLf3EceqgCeIvCbuMlq78IuaTUXjkQZlHe8
G8sAoIEdEpsNNYwkxqKVb7FXAYfCp0Er
=9Mof
-----END PGP SIGNATURE-----

  reply	other threads:[~2013-06-05 10:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201306040922.10235.frank.mehnert@oracle.com>
2013-06-04 11:58 ` Handling NUMA page migration Robin Holt
2013-06-04 12:14   ` Frank Mehnert
2013-06-04 13:34     ` Robin Holt
2013-06-04 14:02     ` Michal Hocko
2013-06-04 18:17       ` Frank Mehnert
2013-06-04 21:54         ` Frank Mehnert
2013-06-05  7:54           ` Michal Hocko
2013-06-05  8:34             ` Frank Mehnert
2013-06-05  8:56               ` Frank Mehnert
2013-06-05  9:10               ` Michal Hocko
2013-06-05  9:32                 ` Frank Mehnert
2013-06-05  9:56                   ` Michal Hocko
2013-06-05 10:22                     ` Frank Mehnert [this message]
2013-06-05 11:41                       ` Michal Hocko
2013-06-04 15:45     ` Jerome Glisse
2013-06-04 17:49       ` Jerome Glisse
2013-06-05 10:10   ` Mel Gorman
2013-06-05 10:35     ` Frank Mehnert
2013-06-05 12:34       ` Mel Gorman
2013-06-06 10:09         ` Frank Mehnert

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=201306051222.32786.frank.mehnert@oracle.com \
    --to=frank.mehnert@oracle.com \
    --cc=holt@sgi.com \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    /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).