From: Mel Gorman <mgorman@suse.de>
To: Hillf Danton <dhillf@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/5] balancenuma: fix typo in handling pmd numa fault
Date: Tue, 20 Nov 2012 14:12:14 +0000 [thread overview]
Message-ID: <20121120141213.GS8218@suse.de> (raw)
In-Reply-To: <CAJd=RBDOAxWeEbjoLvHAt3=P-w1St84oHhfQ5gGox+GoEBF_6A@mail.gmail.com>
On Sat, Nov 17, 2012 at 01:08:35PM +0800, Hillf Danton wrote:
> s/ptep/pmdp/
>
> Also a cleanup packed: use haddr directly.
>
> Btw, will spin if you no longer need the debug trap.
>
Thanks Hillf. I pulled in 1-3 and patch 5 from this. I left patch 4 for
now as the way it's laid out means it needs to check for the max weight.
It's sortof recovered later by checking if selected_nid != this_nid but
it's doing more work than necessary. I'll re-examine this again but
ideally this particular section would be replaced by something smarter.
--
Mel Gorman
SUSE Labs
prev parent reply other threads:[~2012-11-20 14:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-17 5:08 [PATCH 1/5] balancenuma: fix typo in handling pmd numa fault Hillf Danton
2012-11-20 14:12 ` Mel Gorman [this message]
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=20121120141213.GS8218@suse.de \
--to=mgorman@suse.de \
--cc=dhillf@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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