From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: theSeinfeld@users.sourceforge.net, linux-kernel@vger.kernel.org
Cc: libdc1394-devel@lists.sourceforge.net,
linux1394-devel@lists.sourceforge.net
Subject: Re: allocation failed: out of vmalloc space error treating and VIDEO1394 IOC LISTEN CHANNEL ioctl failed problem
Date: Sun, 14 Jan 2007 20:19:18 +0100 (CET) [thread overview]
Message-ID: <tkrat.c0a43c7c901c438c@s5r6.in-berlin.de> (raw)
In-Reply-To: <200701100023.39964.theSeinfeld@users.sf.net>
On 10 Jan, Peter Antoniac wrote:
[...]
> Problem is: how to get the VMALLOC_RESERVED value for the kernel that is
> running? I couldn't find any standard way to do that (something to apply to
> GNU Linux and the like). All the things I could get were the default value
> being 128MiB :) and that is it. Now, I could just put 128, but what if
> somebody changes that, or in some new distro suddenly decides to make it
> different? Even worse, what if it is an old kernel with 64 setting?
[...]
Maybe somebody at LKML has answers?
--
Stefan Richter
-=====-=-=== ---= -===-
http://arcgraph.de/sr/
next parent reply other threads:[~2007-01-14 19:19 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 [this message]
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
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=tkrat.c0a43c7c901c438c@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--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®