Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Giuliano Pochini <pochini@shiny.it>
Cc: Manuel Jander <manuel.jander@mat.utfsm.cl>,
	Alsa Devel list <alsa-devel@lists.sourceforge.net>
Subject: Re: Scatter Gather
Date: Tue, 02 Mar 2004 11:23:04 +0100	[thread overview]
Message-ID: <s5hn06zfszb.wl@alsa2.suse.de> (raw)
In-Reply-To: <XFMail.20040302111633.pochini@shiny.it>

At Tue, 02 Mar 2004 11:16:33 +0100 (CET),
Giuliano Pochini wrote:
> 
> 
> On 02-Mar-2004 Manuel Jander wrote:
> 
> >> Yes.  Every driver using SG must do this.  Look into bt87x.c or
> >> via82xx.c for examples.
> > 
> > Well, i guess in that case the period size loses any relevance in
> > terms of efficiency.
> 
> Efficiency about what ?  If the hardware can be programmed to use
> any period size, then the application is free to choose the size
> it prefers. It's not a bad thing.  NB: the interrupt should be
> generated at the end of the period, not at the end of each block,
> eg. when it crosses the page boundary.

well, it's ok to generate irqs at each page boundary, too, as long as
the driver processes it properly, i.e. calling
snd_pcm_period_elapsed() only at the irq of the end of period.
of course, less irqs are better from the performance viewpoint.


Takashi


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click

      reply	other threads:[~2004-03-02 10:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-27 18:17 Scatter Gather Manuel Jander
2004-03-01 12:52 ` Clemens Ladisch
2004-03-02  4:09   ` Manuel Jander
2004-03-02  8:00     ` Jaroslav Kysela
2004-03-02 10:16     ` Giuliano Pochini
2004-03-02 10:23       ` Takashi Iwai [this message]

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=s5hn06zfszb.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=manuel.jander@mat.utfsm.cl \
    --cc=pochini@shiny.it \
    /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