From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Dave Taht <dave.taht@gmail.com>, "David P. Reed" <dpreed@deepplum.com>
Cc: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
Anthony Minessale II <anthm@freeswitch.org>,
Cake List <cake@lists.bufferbloat.net>,
Ken Rice <krice@freeswitch.org>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cake] mo bettah open source multi-party videoconferncing in an age of bloated uplinks?
Date: Sat, 28 Mar 2020 20:58:08 +0100 [thread overview]
Message-ID: <878sjkl0a7.fsf@toke.dk> (raw)
In-Reply-To: <CAA93jw6o3N-3Yeox5NfP5T9=Ascpa9UXkpgw2fyX4NaMAvb8iA@mail.gmail.com>
Dave Taht <dave.taht@gmail.com> writes:
>> So: 1. We really should rethink how timing-sensitive algorithms are
>> expressed, and it isn't gonna be good to base them on semaphores and
>> threads that run at random rates. That means a very different OS
>> conceptual framework. Can this share with, say, the Linux we know and
>> love - yes, the hardware can be shared. One should be able to
>> dedicate virtual processors that are not running Linux processes, but
>> instead another computational model (dataflow?).
>
> Linux switched to an EDF model for networking in 5.0
Not entirely. There's EDT scheduling, and the TCP stack is mostly
switched over, I think. But as always, Linux evolves piecemal :)
>> 2. EBPF is interesting, because it is more secure, and is again
>> focused on running code at kernel level, event-driven. I think it
>> would be a seriously difficult lift to get it to the point where one
>> could program the networked media processing in BPF.
>
> But there is huge demand for it, so people are writing way more in it
> than i ever ever thought possible... or desirable.
Tell me about it.
We have seen a bit of interest for combining eBPF with realtime, though.
With the upstreaming of the realtime code, support has landed for
running eBPF even on realtime kernels. And we're starting to see a bit
of interest for looking specifically at latency bounds for network
processing (for TSN), including XDP. Nothing concrete yet, though.
-Toke
next prev parent reply other threads:[~2020-03-28 19:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 17:27 Dave Taht
2020-03-27 19:00 ` David P. Reed
2020-03-27 19:12 ` David Lang
2020-03-27 19:36 ` Dave Taht
2020-03-27 20:32 ` Dave Taht
2020-03-28 19:58 ` Toke Høiland-Jørgensen [this message]
2020-03-28 23:15 ` David P. Reed
2020-03-30 10:57 ` Toke Høiland-Jørgensen
2020-03-28 6:53 ` Anthony Minessale II
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
List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878sjkl0a7.fsf@toke.dk \
--to=toke@redhat.com \
--cc=anthm@freeswitch.org \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=dpreed@deepplum.com \
--cc=krice@freeswitch.org \
--cc=make-wifi-fast@lists.bufferbloat.net \
/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