From: Christoph Lameter <christoph@lameter.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Long Format VHPT patches
Date: Thu, 26 Aug 2004 20:19:49 +0000 [thread overview]
Message-ID: <Pine.LNX.4.58.0408261311490.1674@server.home> (raw)
In-Reply-To: <20040825023439.GA15782@cse.unsw.EDU.AU>
One issue that bothers me is that it is no longer possible to swap pte,
pmd and pgd entries via cmpxchg. My page fault scalability patches are based
on that ability. The Itanium can only do a cmpxchg with a 64 bit value.
The long VHPT entries are 32 bytes long.
IMHO the cmpxchg is unavoidable if we want to increase the scalability of
page fault handling because it offers the shortest and most efficient way
to do synchronize updates to the page tables.
The Intel developers manual documents a way to invalidate a long VHPT
entry while updating it. A special pte_cmpxchg would be needed that
invalidates a VHPT via an atomic operation to set the ti bit, then
does the cmpxchg stuff and then validates the VHPT again. The
page fault handler would have to be modified to redo the fault if the ti
bit is set. However, this is may be significantly than a single cmpxchg.
next prev parent reply other threads:[~2004-08-26 20:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 2:34 Long Format VHPT patches Ian Wienand
2004-08-25 17:01 ` Jesse Barnes
2004-08-25 17:12 ` Chen, Kenneth W
2004-08-25 20:17 ` Arun Sharma
2004-08-25 22:46 ` Peter Chubb
2004-08-26 20:19 ` Christoph Lameter [this message]
2004-08-26 21:20 ` Peter Chubb
2004-08-27 17:15 ` Arun Sharma
2004-08-31 5:53 ` Ian Wienand
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=Pine.LNX.4.58.0408261311490.1674@server.home \
--to=christoph@lameter.com \
--cc=linux-ia64@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