linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Nathan Zimmer <nzimmer@sgi.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Nadia Yvette Chambers <nyc@holomorphy.com>,
	Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
	Mel Gorman <mgorman@suse.de>,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mempolicy: convert the shared_policy lock to a rwlock
Date: Thu, 19 Nov 2015 11:50:44 +0100	[thread overview]
Message-ID: <564DA984.2040903@suse.cz> (raw)
In-Reply-To: <564CDA0F.40801@sgi.com>

On 11/18/2015 09:05 PM, Nathan Zimmer wrote:
>
>
> On 11/18/2015 07:50 AM, Vlastimil Babka wrote:
>> At first glance it seems that RCU would be a good fit here and achieve even
>> better lookup scalability, have you considered it?
>>
>
> Originally that was my plan but when I saw how good the results were
> with the rwlock, I chickened out and took the less prone to mistakes way.
>
> I should also note that the 2% time left in system is not from this lookup
> but another area.

Ah, I see, thanks!
Vlastimil

> Nate
>

--
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>

  reply	other threads:[~2015-11-19 10:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-12 17:11 [RFC] mempolicy: convert the shared_policy lock to a rwlock Nathan Zimmer
2015-11-12 21:10 ` David Rientjes
2015-11-17 16:17   ` [PATCH] " Nathan Zimmer
2015-11-18 13:50     ` Vlastimil Babka
2015-11-18 20:05       ` Nathan Zimmer
2015-11-19 10:50         ` Vlastimil Babka [this message]
2015-12-21 13:15     ` Vlastimil Babka

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=564DA984.2040903@suse.cz \
    --to=vbabka@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=n-horiguchi@ah.jp.nec.com \
    --cc=nyc@holomorphy.com \
    --cc=nzimmer@sgi.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;
as well as URLs for NNTP newsgroup(s).