Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Brian J. Tarricone" <bjt23@ece.cornell.edu>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: [Alsa-user] sb live dma buffer alloc failure?
Date: Thu, 13 Feb 2003 09:56:39 +0100	[thread overview]
Message-ID: <s5hbs1gmud4.wl@alsa2.suse.de> (raw)
In-Reply-To: <3E4AD20D.3070703@ece.cornell.edu>

At Wed, 12 Feb 2003 18:00:29 -0500,
Brian J. Tarricone <bjt23@ece.cornell.edu> wrote:
> 
> just a quick update - i installed yesterday's cvs of alsa-driver, and i 
> haven't had any problems (no alloc failures or apps locking up) since 
> then.  i've tried to stress test it a bit (filling up ram, opening and 
> closing the pcm device rapidly), and i'm pleased to say no problems.  i 
> looked at the cvs logs, quite a bit has been done in sg_buf.c since rc7, 
> perhaps something there had an impact?
>  
> even if this is just a side-effect of other work, thanks for the fix, 
> guys ^_^

thanks for your report.

in the cvs version, sg-buffer handler pre-allocates the buffer and
keep it as other buffer types, so that  the buffer re-allocation
wouldn't happen rarely.   so, it's not a side effect :)


ciao,

Takashi


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  reply	other threads:[~2003-02-13  8:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3E40BA0F.9070600@ece.cornell.edu>
2003-02-07 11:56 ` [Alsa-user] sb live dma buffer alloc failure? Takashi Iwai
2003-02-07 19:46   ` Brian J. Tarricone
2003-02-08 17:10     ` laurent.ml
2003-02-10 12:09       ` Takashi Iwai
2003-02-12 23:00   ` Brian J. Tarricone
2003-02-13  8:56     ` Takashi Iwai [this message]
     [not found] ` <wazza.87d6m6he5z.fsf@message.id>
2003-02-07 11:58   ` Takashi Iwai

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=s5hbs1gmud4.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=bjt23@ece.cornell.edu \
    /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