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/
- Follow-Ups:
- Re: allocation failed: out of vmalloc space - use vmalloc=<size> to increase size.
- From: Jon Dufresne <jon.dufresne@infinitevideocorporation.com>
- Re: allocation failed: out of vmalloc space - use vmalloc=<size> to increase size.
- References:
- Re: allocation failed: out of vmalloc space - use vmalloc=<size> to increase size.
- From: "Daniel J Blueman" <daniel.blueman@gmail.com>
- Re: allocation failed: out of vmalloc space - use vmalloc=<size> to increase size.
- From: "H. Peter Anvin" <hpa@zytor.com>
- Re: allocation failed: out of vmalloc space - use vmalloc=<size> to increase size.
- From: Jon Dufresne <jon.dufresne@infinitevideocorporation.com>
- Re: allocation failed: out of vmalloc space - use vmalloc=<size> to increase size.
- Prev by Date: Re: [ANNOUNCE] Btrfs: a copy on write, snapshotting FS
- Next by Date: Re: PC speaker
- Previous by thread: Re: allocation failed: out of vmalloc space - use vmalloc=<size> to increase size.
- Next by thread: Re: allocation failed: out of vmalloc space - use vmalloc=<size> to increase size.
- Index(es):
 |