From: Eliot Blennerhassett <linux@audioscience.com>
To: netdev@vger.kernel.org
Subject: AVB QoS support (IEEE802.1 Qav and Qat)
Date: Thu, 17 Feb 2011 08:51:17 +1300 [thread overview]
Message-ID: <4D5C2AB5.8010009@audioscience.com> (raw)
In-Reply-To: <4D488D9B.5080409@audioscience.com>
Greetings
Can linux network stacks can support the various protocols required by AVB?
It is not clear to me if it already does, and in any case how the setup
would be accessed?
In particular these two standards and the interaction between them
802.1Qat - Stream Reservation Protocol
802.1Qav - Forwarding and Queuing Enhancements for Time-Sensitive
Streams (approved on Dec 10th, 2009)
Qav requires traffic shaping to smooth the traffic flow in guaranteed
stream class. This is afaik based on 1 packet per stream per 125us
Note that in future (maybe already) there will be hardware assist for
this feature in NIC chips.
--
Eliot Blennerhassett
AudioScience Inc.
[1] http://www.ieee802.org/1/pages/avbridges.html
[2]
http://en.wikipedia.org/wiki/Audio_Video_Bridging#Traffic_shaping_for_AV_streams
prev parent reply other threads:[~2011-02-16 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 22:47 AVB support (IEEE802.1 audio/video bridging) Eliot Blennerhassett
2011-02-16 19:51 ` Eliot Blennerhassett [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=4D5C2AB5.8010009@audioscience.com \
--to=linux@audioscience.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).