From: "Stephen C. Tweedie" <sct@redhat.com>
To: Mark_H_Johnson@Raytheon.com
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
linux MM <linux-mm@kvack.org>,
owner-linux-mm@kvack.org,
Shuvabrata Ganguly <sganguly@cse.iitkgp.ernet.in>
Subject: Re: Question about pte_alloc()
Date: Wed, 15 Nov 2000 15:34:58 +0000 [thread overview]
Message-ID: <20001115153458.G3186@redhat.com> (raw)
In-Reply-To: <OF9A0A3560.2E2B9BC3-ON86256998.0052EDF0@hou.us.ray.com>; from Mark_H_Johnson@Raytheon.com on Wed, Nov 15, 2000 at 09:20:52AM -0600
Hi,
On Wed, Nov 15, 2000 at 09:20:52AM -0600, Mark_H_Johnson@Raytheon.com wrote:
>
> Could you please clarify what is meant by...
> "You cannot safely play pte games at interrupt time. You _must_
> do this in the foreground."
> We are concerned because it may block adoption of Linux for one of our
> current applications.
...
> - Can we do this kind of manipulation with the page tables if we modified
> the Linux trap handlers?
Trap handlers are completely different. Page faults already vector
through the trap handlers, and the kernel is quite happy about
performing blocking IO or pte modifications in that context. You
shouldn't have a problem as long as you observe the kernel's VM and
page table locking rules.
Cheers,
Stephen
--
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.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-11-15 15:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-15 15:20 Mark_H_Johnson
2000-11-15 15:34 ` Stephen C. Tweedie [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-15 7:07 Shuvabrata Ganguly
2000-11-14 20:51 ` Kanoj Sarcar
2000-11-15 10:56 ` Stephen C. Tweedie
2000-11-16 0:04 ` Shuvabrata Ganguly
2000-11-15 15:47 ` Stephen C. Tweedie
2000-11-16 20:32 ` Shuvabrata Ganguly
2000-11-16 14:37 ` Ingo Oeser
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=20001115153458.G3186@redhat.com \
--to=sct@redhat.com \
--cc=Mark_H_Johnson@Raytheon.com \
--cc=linux-mm@kvack.org \
--cc=owner-linux-mm@kvack.org \
--cc=sganguly@cse.iitkgp.ernet.in \
/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