From: Benjamin LaHaise <bcrl@redhat.com>
To: "Sottek, Matthew J" <matthew.j.sottek@intel.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: zap_page_range in a module
Date: Fri, 14 Dec 2001 21:31:42 -0500 [thread overview]
Message-ID: <20011214213142.A28867@redhat.com> (raw)
In-Reply-To: <C8C7DD4157F2D411AC7000A0C96B1522016C37D8@fmsmsx58.fm.intel.com>
In-Reply-To: <C8C7DD4157F2D411AC7000A0C96B1522016C37D8@fmsmsx58.fm.intel.com>; from matthew.j.sottek@intel.com on Fri, Dec 14, 2001 at 06:10:52PM -0800
On Fri, Dec 14, 2001 at 06:10:52PM -0800, Sottek, Matthew J wrote:
> >The vm does zap_page_range for you if you're implementing an
> >mmap operation,
>
> It only does zap_page_range() when the memory map is being
> removed right?
Right.
> I have a 64k sliding "window" into a 1MB region. You can only access
> 64k at a time then you have to switch the "bank" to access the next
> 64k. Address 0xa0000-0xaffff is the 64k window. The actual 1MB of
> memory is above the top of memory and not directly addressable by the
> CPU, you have to go through the banks.
Stop right there. You can't do that. The code will deadlock on page
faults for certain usage patterns. It's slow, inefficient and a waste
of effort.
-ben
--
Fish.
next prev parent reply other threads:[~2001-12-15 2:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-15 2:10 zap_page_range in a module Sottek, Matthew J
2001-12-15 2:31 ` Benjamin LaHaise [this message]
2001-12-17 9:32 ` Martin Diehl
2001-12-18 13:04 ` Helge Hafting
-- strict thread matches above, loose matches on Subject: below --
2001-12-14 21:26 Sottek, Matthew J
2001-12-14 22:30 ` Benjamin LaHaise
2001-12-17 9:32 ` Martin Diehl
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=20011214213142.A28867@redhat.com \
--to=bcrl@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.j.sottek@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.