public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Jon Dufresne <jon.dufresne@infinitevideocorporation.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: allocation failed: out of vmalloc space - use vmalloc=<size> to increase size.
Date: Tue, 12 Jun 2007 08:40:32 -0600	[thread overview]
Message-ID: <466EB060.5040708@shaw.ca> (raw)
In-Reply-To: <fa.VH1FnGj5K9OwLz/eErQti4itl2k@ifi.uio.no>

Jon Dufresne wrote:
> I am writing a linux kernel driver for a custom pci device. I am
> developing against the stock fedora 6 kernel on an x86. This device has
> 512 MB of IO memory reserved by BAR 3. Whenever I try to ioremap this
> space I get the error:
> 
> allocation failed: out of vmalloc space - use vmalloc=<size> to increase
> size.
> 
> I think I understand why this is happening. I obviously don't have
> enough vmalloc space to map such a large chunk of memory. I have been
> using Corbet's et el's "Linux Device Drivers", Love's "Linux Kernel
> Development", and many websites as a guide in this development process
> but have yet to come across information that will help me.
> 
> I'm curious if there is a way around this issue. Or a better way of
> handling it so that I can properly map the entire io memory space.

On an i386 kernel you likely just don't have enough address space 
available to map something that big. Your kernel address space is only 
1GB (with the standard 3G/1G user/kernel split) and it somehow has to 
fit in there along with all the other I/O regions, etc. that are mapped 
into kernel address space.

You may just have to remap smaller chunks of the BAR on demand and unmap 
them when you're finished with them.

An x86_64 kernel likely would not have this problem..

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2007-06-12 14:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.VH1FnGj5K9OwLz/eErQti4itl2k@ifi.uio.no>
2007-06-12 14:40 ` Robert Hancock [this message]
2007-06-12 17:01 allocation failed: out of vmalloc space - use vmalloc=<size> to increase size Daniel J Blueman
2007-06-12 18:08 ` H. Peter Anvin
2007-06-12 19:21   ` Jon Dufresne
2007-06-12 20:22     ` H. Peter Anvin
2007-06-18 12:16       ` Jon Dufresne
  -- strict thread matches above, loose matches on Subject: below --
2007-06-12 13:22 Jon Dufresne

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=466EB060.5040708@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=jon.dufresne@infinitevideocorporation.com \
    --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