From: Nick Piggin <nickpiggin@yahoo.com.au>
To: linux-ia64@vger.kernel.org
Subject: pte bit spin lock
Date: Fri, 19 Nov 2004 06:56:17 +0000 [thread overview]
Message-ID: <419D9911.1080306@yahoo.com.au> (raw)
Hi list,
I was wondering if it might be possible to change arch/ia64/kernel/ivt.S
routines that modify pte access bits, to first take a "spin lock bit" in
the pte before any other modifications to it, and clear the lock bit when
done?
And second question, a pte's memory doesn't ever get updated transparently
by the hardware on ia64, does it?
I have been helping Christoph to look at some ways to reduce page_table_lock
locking. It appears that the ptl can be entirely removed by using per-pte
locks, however this can only be efficient if *all* updates to the pte obey
the lock (if not, then all accesses, and the pte-unlock have to be atomic so
the dirty bit doesn't get lost).
And my last question... I wonder if someone might be able to help me do the
assembly for the locking in ivt.S provided it is a small job and I give the
specification? Sorry, I have no idea about ia64 assembly :(
Thanks,
Nick
next reply other threads:[~2004-11-19 6:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 6:56 Nick Piggin [this message]
2004-11-19 18:46 ` pte bit spin lock Luck, Tony
2004-11-19 19:49 ` Christoph Lameter
2004-11-20 0:56 ` Nick Piggin
2004-11-22 18:44 ` Luck, Tony
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=419D9911.1080306@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--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