Re: allocation failed: out of vmalloc space - use vmalloc=<size> to increase size.

[Jon Dufresne <jon.dufresne@infinitevideocorporation.com>]

Ok, thanks for the help.

Now do I actually need to have the memory mapped in kernel space through
ioremap(), in order to have the memory mapped into user space through
remap_pfn_range()? It seems that remap_pfn_range() only requires a
physical address, not a virtual one.

If this is true then I really don't need to map this in kernel space at
all and only in user space, since it will only be manipulated in user
space.

Thanks,
Jon

On Tue, 2007-06-12 at 13:22 -0700, H. Peter Anvin wrote:
> Jon Dufresne wrote:
> > I wasn't completely honest. It is one bar that has 512 MB, however it is
> > being mapped at 4 128 MB chunks. However, I would like them all mapped
> > at once through the lifetime of the driver.
> > 
> > Is there still no chance?
> 
> 128 MB is still definitely on the heavy side.  Try 64 MB and you might
> be able to get away with it.
> 
> 	-hpa
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/