From: "Stephen C. Tweedie" <sct@redhat.com>
To: David Pinedo <dp@fc.hp.com>
Cc: linux-mm@kvack.org, Stephen Tweedie <sct@redhat.com>
Subject: Re: Running out of vmalloc space
Date: Thu, 17 May 2001 18:39:31 +0100 [thread overview]
Message-ID: <20010517183931.V2617@redhat.com> (raw)
In-Reply-To: <3B04069C.49787EC2@fc.hp.com>; from dp@fc.hp.com on Thu, May 17, 2001 at 11:13:00AM -0600
Hi,
On Thu, May 17, 2001 at 11:13:00AM -0600, David Pinedo wrote:
> On Linux, HP supports up to two FX10 boards in the system. In order to
> use two FX10 boards, the kernel driver needs to map the frame buffer and
> control space for both of the boards. That's a lot of address space,
> 2*(16M+32M)=96M to be exact. Using this much virtual address space on a
> stock RH7.1 smp kernel on a system with 0.5G of memory didn't seem to
> be a problem. However, a colleague reported a problem to me on his
> system with 1.0G of memory -- the X server was exiting with an error
> message indicating that it couldn't map both devices.
You obviously want to be able to map this memory into the X server's
virtual address space, but do you really need to map it into the
kernel's VA too?
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-17 17:39 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 [this message]
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
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=20010517183931.V2617@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