netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jerj@coplanar.net
Cc: netdev@vger.kernel.org
Subject: Re: netif_stop_queue() and multiple hardware queues
Date: Sun, 02 Jul 2006 21:52:53 -0700 (PDT)	[thread overview]
Message-ID: <20060702.215253.74723494.davem@davemloft.net> (raw)
In-Reply-To: <44A88293.7060000@coplanar.net>

From: Jeremy Jackson <jerj@coplanar.net>
Date: Sun, 02 Jul 2006 22:36:03 -0400

> I propose that this is an architecture/framework/API issue that the 
> Linux core networking code should be dealing with.

Proposals are worthless if nobody wants to do the work to actually
implement the proposal.

Your tone seems to suggest that you feel if you propose something,
someone will just jump out of their seat and implement your proposal.

That's not how this works :)

  reply	other threads:[~2006-07-03  4:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <43A09D18.9040401@coplanar.net>
2006-07-03  2:36 ` netif_stop_queue() and multiple hardware queues Jeremy Jackson
2006-07-03  4:52   ` David Miller [this message]
2006-07-06 14:29     ` Jeremy Jackson

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=20060702.215253.74723494.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=jerj@coplanar.net \
    --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;
as well as URLs for NNTP newsgroup(s).