From: Alex Shi <alex.shi@intel.com>
To: Tim Chen <tim.c.chen@linux.intel.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Andi Kleen <andi@firstfloor.org>,
Michel Lespinasse <walken@google.com>,
Davidlohr Bueso <davidlohr.bueso@hp.com>,
Matthew R Wilcox <matthew.r.wilcox@intel.com>,
Dave Hansen <dave.hansen@intel.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Rik van Riel <riel@redhat.com>,
Peter Hurley <peter@hurleysoftware.com>,
linux-kernel@vger.kernel.org, linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH v4 1/5] rwsem: check the lock before cpmxchg in down_write_trylock
Date: Thu, 27 Jun 2013 09:32:33 +0800 [thread overview]
Message-ID: <51CB9631.1030508@intel.com> (raw)
In-Reply-To: <1372285674.22432.141.camel@schen9-DESK>
The following line should be added head of commit log on patches 1~4. :)
From: Alex Shi <alex.shi@intel.com>
> Cmpxchg will cause the cacheline bouning when do the value checking,
> that cause scalability issue in a large machine (like a 80 core box).
>
> So a lock pre-read can relief this contention.
>
> Signed-off-by: Alex Shi <alex.shi@intel.com>
--
Thanks
Alex
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Alex Shi <alex.shi@intel.com>
To: Tim Chen <tim.c.chen@linux.intel.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Andi Kleen <andi@firstfloor.org>,
Michel Lespinasse <walken@google.com>,
Davidlohr Bueso <davidlohr.bueso@hp.com>,
Matthew R Wilcox <matthew.r.wilcox@intel.com>,
Dave Hansen <dave.hansen@intel.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Rik van Riel <riel@redhat.com>,
Peter Hurley <peter@hurleysoftware.com>,
linux-kernel@vger.kernel.org, linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH v4 1/5] rwsem: check the lock before cpmxchg in down_write_trylock
Date: Thu, 27 Jun 2013 09:32:33 +0800 [thread overview]
Message-ID: <51CB9631.1030508@intel.com> (raw)
In-Reply-To: <1372285674.22432.141.camel@schen9-DESK>
The following line should be added head of commit log on patches 1~4. :)
From: Alex Shi <alex.shi@intel.com>
> Cmpxchg will cause the cacheline bouning when do the value checking,
> that cause scalability issue in a large machine (like a 80 core box).
>
> So a lock pre-read can relief this contention.
>
> Signed-off-by: Alex Shi <alex.shi@intel.com>
--
Thanks
Alex
next prev parent reply other threads:[~2013-06-27 1:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1372282738.git.tim.c.chen@linux.intel.com>
2013-06-26 22:27 ` [PATCH v4 1/5] rwsem: check the lock before cpmxchg in down_write_trylock Tim Chen
2013-06-26 22:27 ` Tim Chen
2013-06-27 1:32 ` Alex Shi [this message]
2013-06-27 1:32 ` Alex Shi
2013-06-27 15:59 ` Tim Chen
2013-06-27 15:59 ` Tim Chen
2013-06-26 22:27 ` [PATCH v4 2/5] rwsem: remove 'out' label in do_wake Tim Chen
2013-06-26 22:27 ` Tim Chen
2013-06-26 22:28 ` [PATCH v4 3/5] rwsem: remove try_reader_grant label do_wake Tim Chen
2013-06-26 22:28 ` Tim Chen
2013-06-26 22:28 ` [PATCH v4 4/5] rwsem/wake: check lock before do atomic update Tim Chen
2013-06-26 22:28 ` Tim Chen
2013-06-26 22:28 ` [PATCH v4 5/5] rwsem: do optimistic spinning for writer lock acquisition Tim Chen
2013-06-26 22:28 ` Tim Chen
2013-06-26 22:40 ` Davidlohr Bueso
2013-06-26 22:40 ` Davidlohr Bueso
2013-06-26 22:56 ` Tim Chen
2013-06-26 22:56 ` Tim Chen
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=51CB9631.1030508@intel.com \
--to=alex.shi@intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=dave.hansen@intel.com \
--cc=davidlohr.bueso@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew.r.wilcox@intel.com \
--cc=mingo@elte.hu \
--cc=peter@hurleysoftware.com \
--cc=riel@redhat.com \
--cc=tim.c.chen@linux.intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.