From: Sam Leffler <sam@errno.com>
To: Vladimir Kondratiev <vkondra@mail.ru>
Cc: netdev@oss.sgi.com, hadi@cyberus.ca,
Jeff Garzik <jgarzik@pobox.com>,
Kumar Gala <kumar.gala@freescale.com>
Subject: Re: ethernet QoS support?
Date: Fri, 9 Jul 2004 15:34:53 -0700 [thread overview]
Message-ID: <200407091534.53166.sam@errno.com> (raw)
In-Reply-To: <200407092126.43021.vkondra@mail.ru>
On Friday 09 July 2004 11:26 am, Vladimir Kondratiev wrote:
> > So what do you do now?
>
> Waiting. If no support will exist, it simply means we will be unable to use
> QoS provided by modern 802.11. Depending on market development, impact may
> range from being slightly slower relating to Windows clients, to being
> almost completely unable to communicate for traffic like VOIP. Later will
> be the case if most access points will implement QoS as in TGE.
>
> I can now deliver packets accordingly to skb->priority, but if stack have
> different idea for what is proper proportion between different sorts of
> traffic, driver's Tx path will be flooded with low priority frames.
>
> Situation is much worser for streams with admission control. I have no
> mechanism to communicate with stack for such traffic establishment and tear
> down.
FWIW the madwifi net80211 layer parses TOS to calculate priority and sticks it
in the skb. It also calculates the WME AC to form the QoS frame matter.
This is then handed to drivers below. The Atheros driver supports multiple
tx queues in h/w with appropriate scheduling (for 5212 MACs); it uses the AC
to set packets on the appropriate queue.
Clearly it'd be better if upper layers did the TOS stuff. Whatever is done
however should consider the case where the driver (nee h/w) has it's own
queueing/scheduling facilities.
Sam
next prev parent reply other threads:[~2004-07-09 22:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 18:53 ethernet QoS support? Kumar Gala
2004-07-08 19:01 ` Jeff Garzik
2004-07-08 20:00 ` jamal
2004-07-09 7:02 ` Vladimir Kondratiev
2004-07-09 13:18 ` jamal
2004-07-09 13:41 ` Vladimir Kondratiev
2004-07-09 14:33 ` jamal
2004-07-09 18:26 ` Vladimir Kondratiev
2004-07-09 22:34 ` Sam Leffler [this message]
2004-07-10 8:58 ` Vladimir Kondratiev
2004-07-12 8:38 ` Glen Turner
2004-07-12 12:26 ` jamal
2004-07-12 18:17 ` Vladimir Kondratiev
2004-07-13 2:33 ` jamal
2004-07-12 12:18 ` jamal
2004-07-12 18:07 ` Vladimir Kondratiev
2004-07-13 2:26 ` jamal
2004-07-13 2:36 ` jamal
2004-07-09 15:46 ` Kumar Gala
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=200407091534.53166.sam@errno.com \
--to=sam@errno.com \
--cc=hadi@cyberus.ca \
--cc=jgarzik@pobox.com \
--cc=kumar.gala@freescale.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 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).