linux-kernel - Re: allocation failed: out of vmalloc space error treating and VIDEO1394 IOC LISTEN CHANNEL ioctl failed problem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 15 Jan 2007 10:20:22 -0800
From:	Arjan van de Ven <arjan@...radead.org>
To:	Bill Davidsen <davidsen@....com>
Cc:	theSeinfeld@...rs.sourceforge.net,
	linux1394-devel@...ts.sourceforge.net,
	linux-kernel@...r.kernel.org, libdc1394-devel@...ts.sourceforge.net
Subject: Re: allocation failed: out of vmalloc space error treating and  
	VIDEO1394 IOC LISTEN CHANNEL ioctl failed problem


> > 
> I've used vmalloc in the past, and not had a problem, but it is a fair 
> question, how do you find out how much space is available? Other than a 
> binary vmalloc/release loop.

that's a really hard question since it's dynamic;
I suppose a good rule of thumb is "never expect more than 16Mb to work"
(when I said "64Mb" that was for the kernel as a whole, and there's
other users than just "you" :)

if you need that much you probably should redesign your algorithms to
not need vmalloc in the first place....


-- 
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 majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/