From: Clemens Ladisch <clemens@ladisch.de>
To: Henrik Austad <henrik@austad.us>,
"Alexander E. Patrakov" <patrakov@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>,
hansverk@cisco.com, alsa-devel@alsa-project.org,
haustad@cisco.com
Subject: Re: [RFC] AVB - network-based soundcards in ALSA
Date: Tue, 27 May 2014 15:47:40 +0200 [thread overview]
Message-ID: <5384977C.5070009@ladisch.de> (raw)
In-Reply-To: <20140527090216.GB20915@austad.us>
Henrik Austad wrote:
> [...]
> As to moving samples from the buffer onto the network, one approach would
> be to wrap a set of samples and place it into a ready frame with headers
> and bits set and leave it in a buffer for the network layer to pick up.
>
> The exact method here is not clear to me yet, I need to experiment, and
> probably send something off to the networking guys. But before I do that,
> I'd like to have a reasonable sane idea of how ALSA should handle this.
ALSA expects that the sound card hardware fetches samples whenever it
needs them.
For USB and FireWire, there is a short queue of packets; the driver
appends new packets whenever a bunch of older packets has been completed
(as reported by an interrupt).
(This queue is separate from the ALSA ring buffer, which is then never
accessed directly by hardware.)
> The process of evening out the rate of samples is what traffic shaping and
> stream reservation will help you do (or enforce, ymmv), to some extent at
> least. The credit based shaper algorithm is designed to force bursty
> traffic into a steady stream.
In the case of USB and FireWire, the hardware already knows to send
isochronous packets at a rate of 8 kHz.
A 'normal' NIC wouldn't be able to do this. Are there NICs that have
a separate queue for isochronous packets? Or how else can this be
handled?
Regards,
Clemens
next prev parent reply other threads:[~2014-05-27 13:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 13:03 [RFC] AVB - network-based soundcards in ALSA Henrik Austad
2014-05-26 16:21 ` Alexander E. Patrakov
2014-05-27 9:02 ` Henrik Austad
2014-05-27 12:10 ` Alexander E. Patrakov
2014-05-28 9:07 ` Henrik Austad
2014-05-27 13:47 ` Clemens Ladisch [this message]
2014-05-28 9:32 ` Henrik Austad
2014-05-28 13:12 ` Clemens Ladisch
2014-05-27 14:36 ` Takashi Iwai
2014-05-27 16:55 ` Pierre-Louis Bossart
2014-05-28 9:43 ` Henrik Austad
2014-05-28 15:14 ` Pierre-Louis Bossart
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=5384977C.5070009@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=hansverk@cisco.com \
--cc=haustad@cisco.com \
--cc=henrik@austad.us \
--cc=patrakov@gmail.com \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.