From: Mel Gorman <mgorman@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Jones <davej@redhat.com>, Hugh Dickins <hughd@google.com>,
Al Viro <viro@zeniv.linux.org.uk>, Rik van Riel <riel@redhat.com>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Aneesh Kumar <aneesh.kumar@linux.vnet.ibm.com>,
Michel Lespinasse <walken@google.com>,
Kirill A Shutemov <kirill.shutemov@linux.intel.com>,
Sasha Levin <sasha.levin@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@suse.de>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/2] NUMA balancing related fixlets v2
Date: Thu, 2 Oct 2014 19:47:40 +0100 [thread overview]
Message-ID: <1412275662-16201-1-git-send-email-mgorman@suse.de> (raw)
There were a few minor changes so am resending just the two patches that
are mostly likely to affect the bug Dave and Sasha saw and marked them for
stable. I'm less confident it will address Sasha's problem because while
I have not kept up to date, I believe he's also seeing memory corruption
issues in next from an unknown source. Still, it would be nice to see how
they affect trinity testing. I'll send the MPOL_MF_LAZY patch separately
because it's not urgent.
mm/huge_memory.c | 7 +++++--
mm/migrate.c | 5 ++++-
2 files changed, 9 insertions(+), 3 deletions(-)
--
1.8.4.5
next reply other threads:[~2014-10-02 18:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 18:47 Mel Gorman [this message]
2014-10-02 18:47 ` [PATCH 1/2] mm: migrate: Close race between migration completion and mprotect Mel Gorman
2014-10-02 19:20 ` Hugh Dickins
2014-10-02 18:47 ` [PATCH 2/2] mm: numa: Do not mark PTEs pte_numa when splitting huge pages Mel Gorman
2014-10-02 19:28 ` Hugh Dickins
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=1412275662-16201-1-git-send-email-mgorman@suse.de \
--to=mgorman@suse.de \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=davej@redhat.com \
--cc=hughd@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=sasha.levin@oracle.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=walken@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
all inboxes | Powered by JetHome®