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: Wed, 23 May 2001 10:35:18 +0100 [thread overview]
Message-ID: <20010523103518.X8080@redhat.com> (raw)
In-Reply-To: <3B0AF30D.8D25806A@fc.hp.com>; from dp@fc.hp.com on Tue, May 22, 2001 at 05:15:26PM -0600
Hi,
On Tue, May 22, 2001 at 05:15:26PM -0600, David Pinedo wrote:
> I followed up on the suggestion of several folks to not map the graphics
> board into kernel vm space. While investigating how to do that, I
> discovered that the frame buffer space did not need to be mapped -- it
> was already being mapped with the control space. So instead of needing
> (32M+16M)*2=96M of vmalloc space, I only need 32M*2=64M. That change
> seemed easier than figuring out how not to map the board into kernel vm
> space, so...
...so you'll end up with a driver which will work fine as long as
nobody tries to load it in parallel with another driver which tries to
pull the same stunt. It's an easy way out which doesn't work if
everybody takes the same easy way out.
I *really* think you need to be avoiding the mapping in the first
place if at all possible.
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-23 9:35 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
2001-05-18 16:44 ` Christoph Hellwig
2001-05-22 23:15 ` David Pinedo
2001-05-23 9:35 ` Stephen C. Tweedie [this message]
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=20010523103518.X8080@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