mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Peter Antoniac <theSeinfeld@users.sourceforge.net>,
	linux-kernel@vger.kernel.org,
	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 12:48:00 -0800	[thread overview]
Message-ID: <1168807680.3123.1137.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <tkrat.832df3763908c060@s5r6.in-berlin.de>

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


  reply	other threads:[~2007-01-14 20:48 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 [this message]
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=1168807680.3123.1137.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=libdc1394-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=stefanr@s5r6.in-berlin.de \
    --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®