netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Kondratiev <vkondra@mail.ru>
To: netdev@oss.sgi.com
Subject: in-driver QoS
Date: Sun, 6 Jun 2004 21:28:47 +0300	[thread overview]
Message-ID: <200406062128.47070.vkondra@mail.ru> (raw)

I'd like to discuss issue with QoS.

In 802.11 network, there is TGe (or 802.11e), working group, developing QoS 
extensions for 802.11. This group's work is close to finish. Current draft 
should be very close to the final standard.

Currently, according to TGe, NIC will support 4 different priorities (or 
access categories). Let's say, 4 distinct Tx queues will be supported by NIC. 
Each Tx queue have its own parameters.

In addition, there are separate streams (TSPEC's) that should be requested, 
i.e. before use, some initiation procedure should be performed. Sure, there 
is tear down for TSPEC as well.

Roughly, 4 access categories corresponds to diffserv, while TSPEC's - to 
intserv.

Now, question is: how will we support these QoS features in network stack?

Let's start from diffserv, it is easier.

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.

Any ideas how to modify stack to support multiple Tx queues?

Vladimir

             reply	other threads:[~2004-06-06 18:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-06 18:28 Vladimir Kondratiev [this message]
2004-06-07 14:00 ` in-driver QoS Andi Kleen
2004-06-07 20:35   ` Vladimir Kondratiev
2004-06-07 22:59     ` Andi Kleen
2004-06-07 23:38     ` jamal
2004-06-08  5:41       ` Vladimir Kondratiev
2004-06-08 11:28         ` jamal
  -- strict thread matches above, loose matches on Subject: below --
2004-06-08 18:48 Jean Tourrilhes
     [not found] ` <1086722317.1023.18.camel@jzny.localdomain>
2004-06-08 19:52   ` Jean Tourrilhes
2004-06-08 20:55     ` jamal
2004-06-08 22:01       ` Jean Tourrilhes
2004-06-09  3:46         ` jamal
2004-06-09 17:40           ` Jean Tourrilhes
2004-06-10  1:47             ` jamal
2004-06-09  5:51       ` Vladimir Kondratiev
2004-06-09 11:20         ` jamal
2004-06-09 18:27           ` Vladimir Kondratiev
2004-06-10  1:59             ` jamal
2004-06-10  5:55               ` Vladimir Kondratiev
2004-06-11 12:17                 ` jamal
2004-06-10  2:45             ` Horms
     [not found] ` <200406111619.40260.vkondra@mail.ru>
     [not found]   ` <1086960639.1068.697.camel@jzny.localdomain>
2004-06-14 20:53     ` Vladimir Kondratiev
2004-06-15 12:26       ` jamal
2004-06-15 16:35         ` Vladimir Kondratiev

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=200406062128.47070.vkondra@mail.ru \
    --to=vkondra@mail.ru \
    --cc=netdev@oss.sgi.com \
    /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).