From: Mel Gorman <mgorman@suse.de>
To: Andi Kleen <ak@linux.intel.com>
Cc: Andi Kleen <andi@firstfloor.org>,
peterz@infradead.org, linux-mm@kvack.org,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Don't touch single threaded PTEs which are on the right node
Date: Thu, 13 Oct 2016 19:16:37 +0100 [thread overview]
Message-ID: <20161013181637.GF20573@suse.de> (raw)
In-Reply-To: <20161013180402.GI3078@tassilo.jf.intel.com>
On Thu, Oct 13, 2016 at 11:04:02AM -0700, Andi Kleen wrote:
> > > do {
> > > oldpte = *pte;
> > > @@ -94,6 +100,13 @@ static unsigned long change_pte_range(struct vm_area_struct *vma, pmd_t *pmd,
> > > /* Avoid TLB flush if possible */
> > > if (pte_protnone(oldpte))
> > > continue;
> > > +
> > > + /*
> > > + * Don't mess with PTEs if page is already on the node
> > > + * a single-threaded process is running on.
> > > + */
> > > + if (target_node == page_to_nid(page))
> > > + continue;
> > > }
> > >
> >
> > Check target_node != NUMA_NODE && target_node == page_to_nid(page) to
> > avoid unnecessary page->flag masking and shifts?
>
> I didn't do this last change because I expect a potentially mispredicted
> check is more expensive than some shifting/masking.
>
Ok, that's fair enough. For something that minor I expect it to be a
case of "you win some you lose some" depending on workload, CPU and
phase of the moon.
Thanks.
--
Mel Gorman
SUSE Labs
--
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>
next prev parent reply other threads:[~2016-10-13 18:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 16:15 Andi Kleen
2016-10-13 8:39 ` Mel Gorman
2016-10-13 18:04 ` Andi Kleen
2016-10-13 18:16 ` Mel Gorman [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-13 18:08 Andi Kleen
2016-10-11 20:28 Andi Kleen
2016-10-12 5:49 ` Mel Gorman
2016-10-12 15:40 ` Andi Kleen
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=20161013181637.GF20573@suse.de \
--to=mgorman@suse.de \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterz@infradead.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