From: "Venkatesh Ramamurthy" <venkateshr@softhome.net>
To: "Stephen C. Tweedie" <sct@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>
Cc: <linux-kernel@vger.kernel.org>, "Stephen Tweedie" <sct@redhat.com>
Subject: Re: RFC: pageable kernel-segments
Date: Fri, 20 Apr 2001 10:23:53 -0400 [thread overview]
Message-ID: <040201c0c9a5$87d05c60$7253e59b@megatrends.com> (raw)
In-Reply-To: <27525795B28BD311B28D00500481B7601F11D9@ftrs1.intranet.ftr.nl> <9bi53d$5n6$1@cesium.transmeta.com> <20010420131357.B1444@redhat.com>
> > VMS does this. It at least used to have a great tendency to crash
> > itself, because it swapped out something that was called from a driver
> > that was called by the swapper -- resulting in deadlock. You need
> > iron discipline for this to work right in all circumstances.
>
> Actually, VMS doesn't do this, precisely because it is so hard to get
> right. VMS has both paged and non-paged pools for dynamically
> allocated kernel memory, but the kernel code itself is non-pageable.
[Venkat] This [pageable drivers] has been a nightware for NT (derived from
VMS) driver programmers. It almost divides the set of kernel API into two
halves, one which can be called at any IRQL and the other only at elevated
irql. The benefits of having pageable kernel pages is very minimal when
compared to the complexity that gets added to the kernel. We can keep the
kernel simpler(and faster) without having parts of drivers pageable. But one
more issue is having the page tables pageable.......
next prev parent reply other threads:[~2001-04-20 14:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-17 15:57 Heusden, Folkert van
2001-04-17 16:07 ` Disconnect
[not found] ` <01041720013700.02396@idun>
2001-04-20 13:41 ` Disconnect
2001-04-17 19:21 ` H. Peter Anvin
2001-04-17 23:58 ` Albert D. Cahalan
2001-04-20 12:13 ` Stephen C. Tweedie
2001-04-20 14:23 ` Venkatesh Ramamurthy [this message]
2001-04-20 14:49 ` Alan Cox
2001-04-20 15:40 ` Venkatesh Ramamurthy
2001-04-20 18:51 ` Stephen C. Tweedie
2001-04-21 15:48 ` Rik van Riel
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='040201c0c9a5$87d05c60$7253e59b@megatrends.com' \
--to=venkateshr@softhome.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.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
all inboxes | Powered by JetHome®