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 10:56:22 +0200 [thread overview]
Message-ID: <201306051056.22716.frank.mehnert@oracle.com> (raw)
In-Reply-To: <201306051034.19959.frank.mehnert@oracle.com>
[-- Attachment #1: Type: Text/Plain, Size: 2613 bytes --]
On Wednesday 05 June 2013 10:34:13 Frank Mehnert wrote:
> On Wednesday 05 June 2013 09:54:54 Michal Hocko wrote:
> > On Tue 04-06-13 23:54:45, Frank Mehnert wrote:
> > > On Tuesday 04 June 2013 20:17:02 Frank Mehnert wrote:
> > > > On Tuesday 04 June 2013 16:02:30 Michal Hocko wrote:
> > > > > On Tue 04-06-13 14:14:45, Frank Mehnert wrote:
> > > > > > On Tuesday 04 June 2013 13:58:07 Robin Holt wrote:
> > > > > > > This is probably more appropriate to be directed at the
> > > > > > > linux-mm mailing list.
> > > > > > >
> > > > > > > On Tue, Jun 04, 2013 at 09:22:10AM +0200, Frank Mehnert wrote:
> > > > > > > > Hi,
> > > > > > > >
> > > > > > > > our memory management on Linux hosts conflicts with NUMA page
> > > > > > > > migration. I assume this problem existed for a longer time
> > > > > > > > but Linux 3.8 introduced automatic NUMA page balancing which
> > > > > > > > makes the problem visible on multi-node hosts leading to
> > > > > > > > kernel oopses.
> > > > > > > >
> > > > > > > > NUMA page migration means that the physical address of a page
> > > > > > > > changes. This is fatal if the application assumes that this
> > > > > > > > never happens for that page as it was supposed to be pinned.
> > > > > > > >
> > > > > > > > We have two kind of pinned memory:
Just to repeat it for reference:
A) 1. allocate memory in userland with mmap()
2. madvise(MADV_DONTFORK)
3. pin with get_user_pages().
4. flush dcache_page()
5. vm_flags |= (VM_DONTCOPY | VM_LOCKED)
(resulting flags are VM_MIXEDMAP | VM_DONTDUMP | VM_DONTEXPAND |
VM_DONTCOPY | VM_LOCKED | 0xff)
B) 1. allocate memory with alloc_pages()
2. SetPageReserved()
3. vm_mmap() to allocate a userspace mapping
4. vm_insert_page()
5. vm_flags |= (VM_DONTEXPAND | VM_DONTDUMP)
(resulting flags are VM_MIXEDMAP | VM_DONTDUMP | VM_DONTEXPAND | 0xff)
The frequent case is B.
I've just disabled CONFIG_TRANSPARENT_HUGEPAGE for testing purposes and
the Oops is still triggered when running my testcase.
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 --]
next prev parent reply other threads:[~2013-06-05 8:56 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 ` 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 [this message]
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
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=201306051056.22716.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