From: Arjan van de Ven <arjan@infradead.org>
To: Bill Davidsen <davidsen@tmr.com>
Cc: theSeinfeld@users.sourceforge.net,
linux1394-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
libdc1394-devel@lists.sourceforge.net
Subject: Re: allocation failed: out of vmalloc space error treating and VIDEO1394 IOC LISTEN CHANNEL ioctl failed problem
Date: Mon, 15 Jan 2007 10:20:22 -0800 [thread overview]
Message-ID: <1168885223.3122.304.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <45ABC1A2.90109@tmr.com>
> >
> 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
next prev parent reply other threads:[~2007-01-15 18:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.59.1168027378.1221.libdc1394-devel@lists.sourceforge.net>
[not found] ` <200701100023.39964.theSeinfeld@users.sf.net>
2007-01-14 19:19 ` Stefan Richter
2007-01-14 19:28 ` Arjan van de Ven
2007-01-14 20:31 ` Stefan Richter
2007-01-14 20:48 ` Arjan van de Ven
2007-01-15 4:14 ` Peter Antoniac
2007-01-15 6:01 ` Peter Antoniac
2007-01-15 18:02 ` Bill Davidsen
2007-01-15 18:20 ` Arjan van de Ven [this message]
2007-01-15 19:54 ` David Moore
2007-01-15 21:06 ` Kristian Høgsberg
2007-01-15 21:24 ` Arjan van de Ven
2007-01-15 21:43 ` Kristian Høgsberg
2007-01-16 2:40 ` Peter Antoniac
2007-01-16 5:21 ` David Moore
2007-01-16 17:58 ` Arjan van de Ven
2007-01-16 8:16 ` Gerd Hoffmann
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=1168885223.3122.304.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=davidsen@tmr.com \
--cc=libdc1394-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=theSeinfeld@users.sourceforge.net \
/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
all inboxes | Powered by JetHome®