From: Richard Cochran <richardcochran@gmail.com>
To: Henrik Austad <henrik@austad.us>
Cc: linux-kernel@vger.kernel.org, Henrik Austad <haustad@cisco.com>,
linux-media@vger.kernel.org, alsa-devel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [TSN RFC v2 0/9] TSN driver for the kernel
Date: Sat, 17 Dec 2016 21:09:34 +0100 [thread overview]
Message-ID: <20161217200934.GA4797@localhost.localdomain> (raw)
In-Reply-To: <20161217090554.GA19737@icarus.home.austad.us>
On Sat, Dec 17, 2016 at 10:05:54AM +0100, Henrik Austad wrote:
> I'm sending out a new set now because, what I have works _fairly_ well for
> testing and a way to see what you can do with AVB. Using spotify to play
> music on random machines is quite entertaining.
You have missed the point about TSN entirely. Unless your demo has
synchronized playback (in the low microsecond range), then it really
is pointless. We can already play music over the LAN using gstreamer,
without a single kernel change. Heck, gstreamer even has its own
rudimentary synchronization, so your series is a step backwards.
> And therein lies the problem. It cannot yet be written, so we have to start
> in *some* end. And as I repeatedly stated in June, I'm at an RFC here,
> trying to spark some interest and lure other developers in :)
The best way to attract interest is to provide the critical
infrastructure missing in the kernel. Coding a media player in kernel
space is not very interesting in my view.
> Yes, and this requires a lot of change to ALSA (and probably something in
> V4L2 as well?), so before we get to that, perhaps have a set of patches
> that does this best effort and *then* work on getting time-triggered
> playback into the kernel?
No, we don't need a best effort implementation. That is gstreamer and Co.
> So, the next issue I plan to tackle, is how I do buffers, the current
> approach where tsn_core allocates memory is on its way out and I'll let the
> shim (which means alsa/v4l2) will provide a buffer. Then I'll start looking
> at qdisc.
More than once you wrote something like, "I know that's needed, but it
is just too hard ATM." Please start with qdisc and tc. That
shouldn't be too hard. If we had the AVB shaping rules with one or
two drivers supporting them, that would be one piece already done.
Thanks,
Richard
prev parent reply other threads:[~2016-12-17 20:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 17:59 [TSN RFC v2 0/9] TSN driver for the kernel henrik
2016-12-16 17:59 ` [TSN RFC v2 1/9] igb: add missing fields to TXDCTL-register henrik
2016-12-16 17:59 ` [TSN RFC v2 2/9] TSN: add documentation henrik
2016-12-16 17:59 ` [TSN RFC v2 3/9] TSN: Add the standard formerly known as AVB to the kernel henrik
2016-12-16 17:59 ` [TSN RFC v2 4/9] Adding TSN-driver to Intel I210 controller henrik
2016-12-16 17:59 ` [TSN RFC v2 5/9] Add TSN header for the driver henrik
2016-12-16 22:09 ` Richard Cochran
2016-12-17 8:53 ` Henrik Austad
2016-12-16 17:59 ` [TSN RFC v2 6/9] Add TSN machinery to drive the traffic from a shim over the network henrik
2016-12-16 17:59 ` [TSN RFC v2 7/9] Add TSN event-tracing henrik
2016-12-16 17:59 ` [TSN RFC v2 8/9] AVB ALSA - Add ALSA shim for TSN henrik
2016-12-16 17:59 ` [TSN RFC v2 9/9] MAINTAINERS: add TSN/AVB-entries henrik
2016-12-16 18:12 ` [TSN RFC v2 0/9] TSN driver for the kernel Greg
2016-12-16 18:20 ` David Miller
2016-12-16 19:07 ` Henrik Austad
2016-12-16 22:05 ` Richard Cochran
2016-12-17 9:05 ` Henrik Austad
2016-12-17 20:09 ` Richard Cochran [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=20161217200934.GA4797@localhost.localdomain \
--to=richardcochran@gmail.com \
--cc=alsa-devel@vger.kernel.org \
--cc=haustad@cisco.com \
--cc=henrik@austad.us \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--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).