From: "Stephen C. Tweedie" <sct@redhat.com>
To: Martin Frey <frey@scs.ch>
Cc: "'Stephen C. Tweedie'" <sct@redhat.com>,
'Martin Maletinsky' <maletinsky@scs.ch>,
linux-mm@kvack.org
Subject: Re: how has set_pgdir been replaced in 2.4.x
Date: Mon, 10 Dec 2001 15:51:00 +0000 [thread overview]
Message-ID: <20011210155100.D1919@redhat.com> (raw)
In-Reply-To: <00c801c1817e$bc3b4d70$03fe13ac@scs.ch>; from frey@scs.ch on Mon, Dec 10, 2001 at 01:35:19PM +0100
Hi,
On Mon, Dec 10, 2001 at 01:35:19PM +0100, Martin Frey wrote:
> >They are now faulted on demand for vmalloc. The cost of manually
> >updating all the pgds for every vmalloc is just too expensive if
> >you've got tens of thousands of threads in the system.
>
> Is there an implication on drivers, e.g. not accessing vmalloc'd
> memory from within a page fault handler? A page fault from a
> page fault handler is quite ugly...
arch/i386/mm/fault.c is where the magic happens. The vmalloc fault
path is really, really careful not to access any potentially volatile
data, so it is supposed to be safe for use even inside traps and
interrupts.
There _is_ one place where it can break down: if you have a driver
which walks page tables manually after a vmalloc, expecting to
translate virtual addresses into physical ones before the VA has been
faulted in. Other than that, it should be safe.
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-mm.org/
prev parent reply other threads:[~2001-12-10 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-10 8:53 Martin Maletinsky
2001-12-10 10:38 ` Stephen C. Tweedie
2001-12-10 12:35 ` Martin Frey
2001-12-10 15:51 ` Stephen C. Tweedie [this message]
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=20011210155100.D1919@redhat.com \
--to=sct@redhat.com \
--cc=frey@scs.ch \
--cc=linux-mm@kvack.org \
--cc=maletinsky@scs.ch \
/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