From: Hal Murray <hmurray@megapathdsl.net>
To: "David P. Reed" <dpreed@deepplum.com>
Cc: Hal Murray <hmurray@megapathdsl.net>,
"bloat" <bloat@lists.bufferbloat.net>,
"Make-Wifi-fast" <make-wifi-fast@lists.bufferbloat.net>,
"Cake List" <cake@lists.bufferbloat.net>,
"cerowrt-devel" <cerowrt-devel@lists.bufferbloat.net>,
"Ken Rice" <krice@freeswitch.org>,
"Anthony Minessale II" <anthm@freeswitch.org>
Subject: Re: [Cake] [Bloat] mo bettah open source multi-party videoconferncing in an age of bloated uplinks
Date: Fri, 27 Mar 2020 14:34:22 -0700 [thread overview]
Message-ID: <20200327213422.B90CA40605C@ip-64-139-1-69.sjc.megapath.net> (raw)
> I hate putting things in the kernel! It's insecure. But what this says is
> that for very historical and stupid reasons (related to the ideas of early
> timesharing systems like Unix and Multics) folks try to make real-time
> algorithms look like ordinary "processes" whose notion of controlling
> temporal behavior is abstracted away.
Could you please say more.
Why doesn't it work to put the time critical stuff in a separate light weight
thread and give it higher priority than the stuff that needs lots of CPU?
Is the problem in the scheduler? Is background junk overloading the system?
(Are people rebuilding the kernel while video converencing?)
Is it too hard to split out the logic that would go in the light weight
thread? (get tangled on locks or such)
--
These are my opinions. I hate spam.
reply other threads:[~2020-03-27 21:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200327213422.B90CA40605C@ip-64-139-1-69.sjc.megapath.net \
--to=hmurray@megapathdsl.net \
--cc=anthm@freeswitch.org \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--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