General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: "David P. Reed" <dpreed@deepplum.com>, Theodore Ts'o <tytso@mit.edu>
Cc: "Jason A. Donenfeld" <jason@zx2c4.com>,
	Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
	Cake List <cake@lists.bufferbloat.net>,
	cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Cerowrt-devel] wireguard almost takes a bullet
Date: Wed, 31 Mar 2021 10:55:50 -0600	[thread overview]
Message-ID: <875z17mfe1.fsf@meer.lwn.net> (raw)
In-Reply-To: <1617153830.6256867@apps.rackspace.com>

"David P. Reed" <dpreed@deepplum.com> writes:

> Regarding the organizaton of "Linux, Inc." as a hierachical control
> structure - I'll just point out that hierarchical control of the
> development of Linux suggests that it is not at all a "community
> project" (if it ever was). It's a product development organization
> with multiple levels of management.
>  
> Yet the developers are employees of a small number of major
> corporations. In this sense, it is like a "joint venture" among those
> companies.

...where "a small number" == 225 for the 5.11 development cycle; the
biggest of those contributed just under 10% of the patches.

	https://lwn.net/Articles/845831/

It seems rather less concentrated than many projects out there, and it
has become less so over time.

> To the extent that those companies gain (partial) control of the Linux
> kernel, as appears to be the case, I think Linux misrepresents itself
> as a "community project", and in particular, the actual users of the
> software may have little say in the direction development takes going
> forwards.
>  
> There's little safeguard, for example, against "senior management"
> biases in support of certain vendors, if other vendors are excluded
> from effective participation by one of many techniques. In other
> words, there's no way it can be a level playing field for innovation.

I would be curious to hear whether you think there is evidence of
vendors being excluded?  No doubt something has happened somewhere, but
I am unaware if widespread use of "one of many techniques" and would
certainly appreciate being enlightened.

The biggest impediment to innovation in Linux, I think, is the massive
installed user base and the need to never break anything for anybody —
along with the increase in complexity overall.  Just look at what it has
taken (and is still taking) to get us past the year-2038 problem
relative to how some other systems have been able to just deal with it,
for example.

WireGuard, which started this discussion, is a good example to look at
it.  This was definitely an innovative development, brought in by a
developer previously unknown to the community and, as far as I know, not
in the thrall of any of the corporations contributing to the Linux
kernel.  Jason had to jump through all sorts of hoops to get it in, but
that wasn't the result of anybody trying to block it - we wanted it!
But it did need to fit into what we had already, and that took some
work. 

Thanks,

jon

  parent reply	other threads:[~2021-03-31 16:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-28 15:56 [Bloat] " Dave Taht
2021-03-29 20:28 ` [Bloat] [Cerowrt-devel] " David P. Reed
2021-03-29 21:02   ` Dave Taht
2021-03-30  1:52   ` Theodore Ts'o
2021-03-31  1:23     ` David P. Reed
2021-03-31  2:04       ` [Bloat] [Make-wifi-fast] " David Lang
2021-03-31  4:15       ` [Bloat] " Dave Taht
2021-03-31 17:37         ` Theodore Ts'o
2021-03-31 16:08       ` Theodore Ts'o
2021-03-31 16:55       ` Jonathan Corbet [this message]
2021-03-31  2:18   ` Embedded Devel

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/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875z17mfe1.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dpreed@deepplum.com \
    --cc=jason@zx2c4.com \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=tytso@mit.edu \
    /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