From: Guenter Roeck <linux@roeck-us.net>
To: Theodore Ts'o <tytso@mit.edu>,
Ben Collins <benmcollins13@gmail.com>,
David Miller <davem@davemloft.net>,
afleming@freescale.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH] net: Add support for handling queueing in hardware
Date: Sat, 23 Mar 2013 12:10:23 -0700 [thread overview]
Message-ID: <20130323191023.GB22005@roeck-us.net> (raw)
In-Reply-To: <20130322220840.GA6647@thunk.org>
On Fri, Mar 22, 2013 at 06:08:40PM -0400, Theodore Ts'o wrote:
> On Fri, Mar 22, 2013 at 11:39:20AM -0400, Ben Collins wrote:
> >
> > If your company had hardware going to production, you'd want it supported in mainline too, I suspect.
>
> And if companies told their hardware partners that they will drop use
> of their hardware in future products unless they get their !@#@S
> drivers upstream, I'd bet they'd change their engineering priorities
> so they would work on it, instead of foisting this work on their
> customers.
>
I would love to be in that position. However, the decision to choose
a specific chip is not always coordinated with those who have to provide
the software to run on those chips.
> I've seen this work in enterprise computing, where the RFP had
> requirements for upstream drivers (i.e., if you want your 10gig
> ethernet NIC to be used in HP or IBM's servers, get the darned thing
> upstream!). The trick is making it clear that selection of components
> depends not just on an OSS driver, but an OSS driver which has been
> accepted upstream (which also helps from a quality-of-code
> requirement).
>
> I've been waiting for this to start happening in the consumer
> electronics/embedded world, but it's been slow coming,
> unfortunately....
>
The same applies to vendors of non-consumer network devices, unfortunately.
Guenter
next prev parent reply other threads:[~2013-03-24 9:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 13:52 [PATCH] net: Add support for handling queueing in hardware Andy Fleming
2013-03-22 14:11 ` David Miller
2013-03-22 14:31 ` Fleming Andy-AFLEMING
2013-03-22 14:33 ` David Miller
2013-03-22 14:43 ` Ben Collins
2013-03-22 15:17 ` David Miller
2013-03-22 15:39 ` Ben Collins
2013-03-22 15:41 ` David Miller
2013-03-22 15:53 ` Ben Collins
2013-03-22 15:59 ` David Miller
2013-03-22 16:14 ` Ben Collins
2013-03-22 16:16 ` David Miller
2013-03-22 16:23 ` Ben Collins
2013-03-22 22:08 ` Theodore Ts'o
2013-03-23 19:10 ` Guenter Roeck [this message]
2013-04-01 14:13 ` Mark Brown
2013-03-23 19:02 ` Guenter Roeck
2013-03-24 19:06 ` Guenter Roeck
2013-03-22 14:23 ` Eric Dumazet
2013-03-22 14:50 ` Ben Collins
2013-03-22 15:01 ` Eric Dumazet
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=20130323191023.GB22005@roeck-us.net \
--to=linux@roeck-us.net \
--cc=afleming@freescale.com \
--cc=benmcollins13@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).