From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: mingo@redhat.com, torvalds@transmeta.com, linux-mm@kvack.org,
linux-kernel@vger.rutgers.edu
Subject: Re: set_pte() is no longer atomic with PAE36.
Date: Thu, 2 Dec 1999 14:42:45 +0000 (GMT) [thread overview]
Message-ID: <E11tXRX-0000sQ-00@the-village.bc.nu> (raw)
In-Reply-To: <199912021427.OAA03199@dukat.scot.redhat.com> from "Stephen C. Tweedie" at Dec 2, 99 02:27:47 pm
> Modifying an existing pte (eg. for COW) is probably even harder: do we
> need to clear the page-present bit while we modify the high word?
> Simply setting the dirty or accessed bits should pose no such problem,
> but relocating a page looks as if it could bite here.
You can do 64bit atomic sets with lock cmpxchg8. It might just be slow though
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
next prev parent reply other threads:[~1999-12-02 14:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-02 14:27 Stephen C. Tweedie
1999-12-02 14:42 ` Alan Cox [this message]
1999-12-02 14:50 ` Ingo Molnar
1999-12-02 15:54 ` Ingo Molnar
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=E11tXRX-0000sQ-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=sct@redhat.com \
--cc=torvalds@transmeta.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