All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Vladimir Kondratiev <vkondra@mail.ru>
Cc: James Ketrenos <jketreno@linux.jf.intel.com>,
	Netdev <netdev@oss.sgi.com>
Subject: Re: Fwd: in-driver QoS
Date: Mon, 07 Jun 2004 15:38:23 -0400	[thread overview]
Message-ID: <40C4C42F.2040006@pobox.com> (raw)
In-Reply-To: <200406072217.31924.vkondra@mail.ru>

Vladimir Kondratiev wrote:
> skb->priority help determining Tx queue, but fundamental problem is with
> single Tx queue from network stack. Any smart queuing/scheduling etc. made by
> driver, will render useless while network stack provides single Tx queue.


The packet schedulers already have multiple queues, why isn't the packet 
scheduling framework sufficient?

Who cares if there is a single TX "delivery point" to the driver, as 
long as the driver knows how to differentiate queues.

	Jeff

       reply	other threads:[~2004-06-07 19:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200406072217.31924.vkondra@mail.ru>
2004-06-07 19:38 ` Jeff Garzik [this message]
2004-06-07 20:28   ` Fwd: in-driver QoS Vladimir Kondratiev
2004-06-07 22:58     ` Andi Kleen

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=40C4C42F.2040006@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=jketreno@linux.jf.intel.com \
    --cc=netdev@oss.sgi.com \
    --cc=vkondra@mail.ru \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.