From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "dpreed@deepplum.com" <dpreed@deepplum.com>
Cc: Dave Taht <dave.taht@gmail.com>, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] So how far behind is the embedded router world, still?
Date: Thu, 26 Jul 2018 15:56:39 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1807261552300.14354@uplift.swm.pp.se> (raw)
In-Reply-To: <1532610827.31646803@apps.rackspace.com>
On Thu, 26 Jul 2018, dpreed@deepplum.com wrote:
> Why not now?
Problem I am seeing is that there aren't enough abstraction frameworks,
and creating these might take years. I saw Linus argued against ARM
developers who kept coming with their SoC-unique patch-sets, and told them
to go home and come back with something more generic. This actually
happened.
We have *not* seen this for packet accelerators for instance. I have
advocated Linux Foundation to do this, they know the issue, it's something
we all want to fix, but it needs customers to push OEMs to push SoC
vendors to do this. It's a classical "everybody benefits in the long run,
but short term there is no immediate benefit" kind of thing.
Your example of PCI is classic, I see lots of Open* innitiatives but
they're typically quasi-open, the source is open, but the work is done
behind closed doors and code is thrown over the fence.
To me it's amazing that Linux kernel has gotten as far as it has, and
actually has a so-so working community around it, with lots of companies
funding work going in there. Things could be a lot worse.
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2018-07-26 13:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 13:13 [Cerowrt-devel] So how far behind is the embedded router world,still? dpreed
2018-07-26 13:56 ` Mikael Abrahamsson [this message]
2018-07-26 16:45 ` [Cerowrt-devel] So how far behind is the embedded router world, still? valdis.kletnieks
-- strict thread matches above, loose matches on Subject: below --
2018-07-27 12:18 dpreed
2018-07-25 18:50 Dave Taht
2018-07-25 19:14 ` valdis.kletnieks
2018-07-25 19:49 ` dpreed
2018-07-25 20:00 ` Dave Taht
2018-07-25 20:17 ` Jim Gettys
2018-07-26 8:53 ` Mikael Abrahamsson
2018-07-26 14:13 ` Jonathan Morton
2018-07-26 16:48 ` dpreed
2018-07-26 20:15 ` Dave Taht
2018-07-26 20:34 ` Joel Wirāmu Pauling
2018-07-27 9:31 ` Mikael Abrahamsson
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1807261552300.14354@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=dpreed@deepplum.com \
/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