From: holt@sgi.com
To: Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>
Cc: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
Venkatesh Pallipadi <venkatesh.pallipadi@gmail.com>,
Suresh Siddha <suresh.b.siddha@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
x86@kernel.org
Subject: [patch 0/2] x86,pat: Reduce contention on the memtype_lock -V3
Date: Mon, 15 Mar 2010 08:21:03 -0500 [thread overview]
Message-ID: <20100315132103.228021253@gulag1.americas.sgi.com> (raw)
Tracking memtype on x86 uses a single global spin_lock for either reading
or changing the memory type. This includes changes made to page flags
which is perfectly parallel.
Part one of the patchset makes the page-based tracking use cmpxchg
without a need for a lock.
Part two of the patchset converts the spin_lock into a read/write lock.
To: Ingo Molnar <mingo@redhat.com>
To: H. Peter Anvin <hpa@zytor.com>
To: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Robin Holt <holt@sgi.com>
Cc: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Cc: Venkatesh Pallipadi <venkatesh.pallipadi@gmail.com>
Cc: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: x86@kernel.org
---
arch/x86/include/asm/cacheflush.h | 44 +++++++++++++++++++++-----------------
arch/x86/mm/pat.c | 28 ++++++++----------------
2 files changed, 35 insertions(+), 37 deletions(-)
next reply other threads:[~2010-03-15 13:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 13:21 holt [this message]
2010-03-15 13:21 ` [patch 1/2] x86,pat Update the page flags for memtype atomically instead of using memtype_lock. -V3 holt
2010-03-17 10:18 ` Robin Holt
2010-03-17 16:21 ` Suresh Siddha
2010-03-23 23:21 ` Rafael J. Wysocki
2010-03-15 13:21 ` [patch 2/2] x86,pat Convert memtype_lock into an rw_lock holt
2010-03-17 16:21 ` Suresh Siddha
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=20100315132103.228021253@gulag1.americas.sgi.com \
--to=holt@sgi.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@gmail.com \
--cc=venkatesh.pallipadi@intel.com \
--cc=x86@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
all inboxes | Powered by JetHome®