* How device could assemble qdisc for self?
@ 2004-06-16 20:57 Vladimir Kondratiev
2004-06-16 21:07 ` Vladimir Kondratiev
0 siblings, 1 reply; 2+ messages in thread
From: Vladimir Kondratiev @ 2004-06-16 20:57 UTC (permalink / raw)
To: netdev; +Cc: jamal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I am a bit confused looking at qdisc related stuff. Could someone please point
me to right documentation, code to look for etc?
I'd like to employ NIC with many Tx DMA queues, designated for different types
of traffic. Jamal pointed to qdiscs as a way to do it.
My current idea is as following:
I need to arrange the following qdisc structure:
- - total 6 queues (FIFO) maintained;
- - 4 queues get packets accordingly to 802.1D priority tags (some simple fixed
mapping, actually those described in TGe - standard for wireless QoS)
Table follows, but really it does not matter.
802.1D queue(access category)
1 AC_BK Background
2 AC_BK
0 AC_BE Best effort
3 AC_BE
4 AC_VI Video
5 AC_VI
6 AC_VO Voice
7 AC_VO
- - 1 queue used for all bcast/mcast packets (wireless AP need it)
- - 1 queue used for packets marked by application in some specific way (don't
know how exactly, long story, next time)
Each queue corresponds to one tx DMA queue within NIC. Each one should be
stopped/started separately. Then, in hard_start_xmit, I will select proper
DMA queue based on skb->priority. When DMA queue is full, I will stop
corresponding qdisc.
Does this structure make sense? Could it be done easier?
Vladimir
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFA0LRNqxdj7mhC6o0RAvaMAJ4kr7le3zZQbspb5biMsexbJSi/HwCgiwyJ
gDn2m3VujWZuoGgOhWClwhI=
=ygYp
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: How device could assemble qdisc for self?
2004-06-16 20:57 How device could assemble qdisc for self? Vladimir Kondratiev
@ 2004-06-16 21:07 ` Vladimir Kondratiev
0 siblings, 0 replies; 2+ messages in thread
From: Vladimir Kondratiev @ 2004-06-16 21:07 UTC (permalink / raw)
To: netdev; +Cc: jamal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Forget to mention,
after these 6 qdiscs I described, there is round robin scheduler that do
actually sends packets to hard_start_xmit.
On Wednesday 16 June 2004 23:57, Vladimir Kondratiev wrote:
> Hi,
> I am a bit confused looking at qdisc related stuff. Could someone please
> point me to right documentation, code to look for etc?
>
> I'd like to employ NIC with many Tx DMA queues, designated for different
> types of traffic. Jamal pointed to qdiscs as a way to do it.
>
> My current idea is as following:
>
> I need to arrange the following qdisc structure:
>
> - total 6 queues (FIFO) maintained;
>
> - 4 queues get packets accordingly to 802.1D priority tags (some simple
> fixed mapping, actually those described in TGe - standard for wireless QoS)
> Table follows, but really it does not matter.
>
> 802.1D queue(access category)
> 1 AC_BK Background
> 2 AC_BK
> 0 AC_BE Best effort
> 3 AC_BE
> 4 AC_VI Video
> 5 AC_VI
> 6 AC_VO Voice
> 7 AC_VO
>
> - 1 queue used for all bcast/mcast packets (wireless AP need it)
>
> - 1 queue used for packets marked by application in some specific way
> (don't know how exactly, long story, next time)
>
> Each queue corresponds to one tx DMA queue within NIC. Each one should be
> stopped/started separately. Then, in hard_start_xmit, I will select proper
> DMA queue based on skb->priority. When DMA queue is full, I will stop
> corresponding qdisc.
>
> Does this structure make sense? Could it be done easier?
>
> Vladimir
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFA0Lauqxdj7mhC6o0RAlGNAJ4m9ffMI2ZQ5t74rfVnRh5pVNfpIwCfWm0D
aRk5Ox9agY1yjL6NzC8kOyI=
=k8Eo
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-06-16 21:07 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-06-16 20:57 How device could assemble qdisc for self? Vladimir Kondratiev
2004-06-16 21:07 ` Vladimir Kondratiev
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).