On Sun, 2007-01-14 at 21:31 +0100, Stefan Richter wrote: > On 14 Jan, Arjan van de Ven wrote: > > vmalloc space is limited; you really can't assume you can get any more > > than 64Mb or so (and even then it's thight on some systems already); > > I suppose "grep VmallocChunk /proc/meminfo" shows what is available? > > > it really sounds like vmalloc space isn't the right solution for your > > problem whatever it is (context is lost in the quoted mail)... > > can you restate the problem to see if there's a better solution > > possible? > > Thanks. Below is Peter's message to linux1394-devel. The previous > discussion went over libdc1394-devel which I don't receive. Obviously he > wants a really large buffer for reception of an isochronous stream. I > guess his reason is highly application specific...
but why does that even use vmalloc? You can just do a scatter gather thing instead... and keep a list of pages that you're mapping into userspace. vmalloc isn't really a requirement for that.... -- if you want to mail me at work (you don't), use arjan (at) linux.intel.com Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
