Path: news.mitre.org!blanket.mitre.org!agate!newsgate.duke.edu!nntprelay.mathworks.com!newsfeed.internetmci.com!205.252.116.205!howland.erols.net!usc!newshub.cts.com!newsfeed.cts.com!cmkrnl!jeh
From: jeh@cmkrnl.com (Jamie Hanrahan)
Newsgroups: comp.os.ms-windows.programmer.nt.kernel-mode
Subject: Re: Page fault at DISPATCH_LEVEL
Message-ID: <1997Nov27.091228.8342@cmkrnl>
Date: 27 Nov 97 09:12:28 PST
References: <880387003.1765@dejanews.com> <1997Nov25.173646.8329@cmkrnl> <3485cc4d.378952453@news.alt.net>
Organization: Kernel Mode Systems, San Diego, CA
Lines: 23

In article <3485cc4d.378952453@news.alt.net>, tony@ercolano.com (Anthony V. Ercolano) writes:
> What do you do when you incur a page fault from the DPC routine of a
> disk stack (e.g. atdisk).  Don't see how that fault will ever be
> processed.  The IO that incured the fault can't proceed until the
> queued IO for the fault completes

*whacks self on head*   Duh, I knew that...

> Jamies answer seems the broader perspective.

Covers more bases, true, but I missed the above. Thanks!

> However, I can't shake the feeling that I'm not remembering something
> even more basic.

Same here.

	--- Jamie Hanrahan, Kernel Mode Systems, San Diego CA
        Internet: jeh@cmkrnl.com (JH645)  CompuServe: 74140,2055  
drivers, internals, networks, applications, and training for VMS and Windows NT
NT driver FAQ, links, and other information:  http://www.cmkrnl.com/

If you post a reply in news, please don't e-mail it too.