From: "Stephen C. Tweedie" <sct@redhat.com>
To: David Pinedo <dp@fc.hp.com>
Cc: linux-mm@kvack.org
Subject: Re: Running out of vmalloc space
Date: Fri, 18 May 2001 12:53:54 +0100 [thread overview]
Message-ID: <20010518125354.D8080@redhat.com> (raw)
In-Reply-To: <3B045546.312BA42E@fc.hp.com>; from dp@fc.hp.com on Thu, May 17, 2001 at 04:48:38PM -0600
Hi,
On Thu, May 17, 2001 at 04:48:38PM -0600, David Pinedo wrote:
> Unfortunately, yes. It has to be in the kernel's virtual address space,
> because the kernel graphics driver initiates DMAs to and from the
> graphics board, which can only be done from the kernel using locked down
> physical memory.
Why does it have to be virtually contiguous? If you are using vmalloc
then you are necessarily using physically-discontiguous space. If you
are doing DMA on that space then the kernel isn't accessing it
virtually at all, except perhaps to populate it, which can be done
trivially page by page without having the space virtually contiguous.
It is often a lot easier on the kernel programmer if the addresses
are virtually contiguous, but it is very rarely necessary. It is
trivial to create an "offset_to_virt" helper function which translates
an offset within one of your pci regions to a virtual kernel address
by indexing a physical page location array which contains the list of
allocated pages. The *only* thing which is measurably more difficult
without vmalloc is crossing page boundaries.
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.eu.org/Linux-MM/
next prev parent reply other threads:[~2001-05-18 11:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-17 17:13 David Pinedo
2001-05-17 17:39 ` Stephen C. Tweedie
2001-05-17 22:48 ` David Pinedo
2001-05-18 11:24 ` Andi Kleen
2001-05-18 11:53 ` Stephen C. Tweedie [this message]
2001-05-18 16:44 ` Christoph Hellwig
2001-05-22 23:15 ` David Pinedo
2001-05-23 9:35 ` Stephen C. Tweedie
2001-05-23 16:14 ` David Pinedo
2001-05-23 16:45 ` Stephen C. Tweedie
2001-05-26 5:13 ` Andrew Morton
2001-05-17 19:16 ` Matti Aarnio
2001-05-17 19:23 ` Christoph Hellwig
2001-05-17 20:10 ` Matti Aarnio
2001-05-17 18:51 Hua Ji
2001-05-17 20:17 ` Andi Kleen
2001-05-17 21:58 Hua Ji
2001-05-18 8:21 ` Matti Aarnio
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=20010518125354.D8080@redhat.com \
--to=sct@redhat.com \
--cc=dp@fc.hp.com \
--cc=linux-mm@kvack.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