From: Ben Collins <benmcollins13@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: afleming@freescale.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH] net: Add support for handling queueing in hardware
Date: Fri, 22 Mar 2013 10:43:44 -0400 [thread overview]
Message-ID: <FE78128C-01DB-4831-ACBE-BA3E3A428BFC@gmail.com> (raw)
In-Reply-To: <20130322.103302.1277256650283142022.davem@davemloft.net>
On Mar 22, 2013, at 10:33 AM, David Miller <davem@davemloft.net> wrote:
> From: Fleming Andy-AFLEMING <afleming@freescale.com>
> Date: Fri, 22 Mar 2013 14:31:50 +0000
>
>> It would appear one of our customers is attempting to upstream our
>> code for us. We are aware that this current solution is unacceptable
>> (which is why we have not submitted it), and we are currently trying
>> to develop a less hacky solution that integrates with qdisc.
>
> Ben, can can you coordinate with people instead of doing crap like
> this?
"For us" is a loose term, when it's more that we are attempting to upstream code so our system is supported by a mainline kernel instead of having one-off kernels.
And we have been talking with Freescale about this for quite some time (couple years?). They have a roadmap that doesn't include getting this driver supported in mainline any time soon, so I'm taking time to get this done for our own system. I'm not meaning to step on any toes.
Believe me, I've attempted to make this as painless as possible. Only having 5 patches (and each just a few lines) is significantly less than how this driver started out. I can toss out the QDisc patch and work on a better way. I'm not totally familiar with the queueing, so any pointers to a better way to handle this would be appreciated.
--
Servergy : http://www.servergy.com/
SwissDisk : http://www.swissdisk.com/
Ubuntu : http://www.ubuntu.com/
My Blog : http://ben-collins.blogspot.com/
next prev parent reply other threads:[~2013-03-22 14:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 13:52 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 [this message]
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
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=FE78128C-01DB-4831-ACBE-BA3E3A428BFC@gmail.com \
--to=benmcollins13@gmail.com \
--cc=afleming@freescale.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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
all inboxes | Powered by JetHome®