From: volodya@mindspring.com
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mm question
Date: Mon, 10 Dec 2001 08:47:58 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.20.0112100844210.17065-100000@node2.localnet.net> (raw)
In-Reply-To: <E16DQl3-00023R-00@the-village.bc.nu>
On Mon, 10 Dec 2001, Alan Cox wrote:
> > How does one do the following task: obtain a bunch of free pages (around
> > 300K) with physical addresses between certain bounds (more then
> > 0x4000000, but it is likely this is not constant) reserver them and map to
> > kernel space so that the driver can access them directly ?
>
> We support allocating pages below 16Mb, below 4Gb, or anywhere within RAM
> on x86. If you want to within a range or your 300K must be a single 300K
> block then you need to allocate it at boot time
>
It does not have to be contiguous. I was thinking of simply starting with
the smallest address and trying to free the pages until the needed amount
is available. But I have no idea how to properly do locking or force the
page to be swapped out or something.
As for doing this during boot time this does not seem like a good idea for
two reasons:
a) I need at least _two_ buffers 300K each
b) the actual amount of RAM needed changes depending on video standard
(this is for video capture).
thanks
Vladimir Dergachev
next prev parent reply other threads:[~2001-12-10 13:50 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-10 13:25 volodya
2001-12-10 13:46 ` Alan Cox
2001-12-10 13:47 ` volodya [this message]
2001-12-10 14:07 ` Alan Cox
2001-12-10 15:03 ` volodya
2001-12-10 15:21 ` Alan Cox
2001-12-10 15:40 ` Rik van Riel
2001-12-10 16:14 ` volodya
2001-12-10 16:48 ` Rik van Riel
2001-12-10 17:02 ` volodya
2001-12-10 17:16 ` Alan Cox
2001-12-10 17:29 ` volodya
2001-12-10 18:05 ` Rik van Riel
2001-12-10 18:08 ` volodya
2001-12-10 18:17 ` Rik van Riel
2001-12-10 21:30 ` volodya
2001-12-10 18:26 ` Alan Cox
2001-12-10 21:27 ` volodya
2001-12-10 21:42 ` Alan Cox
2001-12-11 1:52 ` volodya
2001-12-11 8:47 ` Eric W. Biederman
2001-12-11 11:07 ` volodya
2001-12-11 18:39 ` Daniel Phillips
2001-12-10 16:05 ` volodya
2001-12-10 17:09 ` Martin J. Bligh
2001-12-10 17:16 ` Martin J. Bligh
2001-12-10 17:26 ` volodya
2001-12-10 17:25 ` Alan Cox
2001-12-10 17:38 ` volodya
2001-12-10 17:51 ` Alan Cox
2001-12-10 17:43 ` volodya
2001-12-10 18:12 ` Alan Cox
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=Pine.LNX.4.20.0112100844210.17065-100000@node2.localnet.net \
--to=volodya@mindspring.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/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®