Discussion:
ath9k-based Mesh uses EDCA or DCF
mohamad.sbeiti-ncST9ati83jjhi9iKp3Nug@public.gmane.org via Devel
2014-10-21 06:38:08 UTC
Permalink
Dear all,

I am wondering whether the implementation of the IEEE 802.11s in case of ath9k relies on the Enhanced Distributed Coordination Function (EDCA) to access the medium and not on the Distributed Coordination Function (DCF). Unfortunately, I could not find any information on this issue in the corresponding debugfs files of ath9k (I am running a small mesh testbed). I would greatly appreciate any hints on this topic.

Best regards
Mohamad

--
Dipl.-Ing. Mohamad Sbeiti
Communication Networks Institute (CNI)
Technische Universität Dortmund
Otto-Hahn-Strasse 6
D-44227 Dortmund, Germany

Fon: +49(0)2 31/755-6128
Fax: +49(0)2 31/755-6136
Room: IRF 202
http://www.kn.e-technik.tu-dortmund.de/

Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender und vernichten Sie diese Mail. Vielen Dank.
Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung eines solchen Schriftstücks per Telefax erfolgen.

Important note: The information included in this e-mail is confidential. It is solely intended for the recipient. If you are not the intended recipient of this e-mail please contact the sender and delete this message. Thank you. Without prejudice of e-mail correspondence, our statements are only legally binding when they are made in the conventional written form (with personal signature) or when such documents are sent by fax.
Yeoh Chun-Yeow via Devel
2014-10-21 09:48:14 UTC
Permalink
Try take a look on the ath9k_conf_tx in ath9k/main.c.

The setting of aifs, cw_min , cw_max and txop may make sense to you.

----
ChunYeow

On Tue, Oct 21, 2014 at 2:38 PM, ***@tu-dortmund.de via
Devel <***@lists.open80211s.org> wrote:
> Dear all,
>
> I am wondering whether the implementation of the IEEE 802.11s in case of ath9k relies on the Enhanced Distributed Coordination Function (EDCA) to access the medium and not on the Distributed Coordination Function (DCF). Unfortunately, I could not find any information on this issue in the corresponding debugfs files of ath9k (I am running a small mesh testbed). I would greatly appreciate any hints on this topic.
>
> Best regards
> Mohamad
>
> --
> Dipl.-Ing. Mohamad Sbeiti
> Communication Networks Institute (CNI)
> Technische Universität Dortmund
> Otto-Hahn-Strasse 6
> D-44227 Dortmund, Germany
>
> Fon: +49(0)2 31/755-6128
> Fax: +49(0)2 31/755-6136
> Room: IRF 202
> http://www.kn.e-technik.tu-dortmund.de/
>
> Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender und vernichten Sie diese Mail. Vielen Dank.
> Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung eines solchen Schriftstücks per Telefax erfolgen.
>
> Important note: The information included in this e-mail is confidential. It is solely intended for the recipient. If you are not the intended recipient of this e-mail please contact the sender and delete this message. Thank you. Without prejudice of e-mail correspondence, our statements are only legally binding when they are made in the conventional written form (with personal signature) or when such documents are sent by fax.
> _______________________________________________
> Devel mailing list
> ***@lists.open80211s.org
> http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
mohamad.sbeiti-ncST9ati83jjhi9iKp3Nug@public.gmane.org via Devel
2014-10-21 15:04:45 UTC
Permalink
thank you for this hint. By printing the values (see below), I found out that the MAC implementation always use EDCA with best effort as the default traffic class!

Best regards
Mohamad

Mesh IEEE802.11s based on IEEE802.11g - channel 6:
Unit 1
[ 4701.352053] ath: phy4: Configure tx [queue/halq] [0/0], aifs: 2, cw_min: 7, cw_max: 15, txop: 102
[ 4701.352097] ath: phy4: Configure tx [queue/halq] [1/1], aifs: 2, cw_min: 15, cw_max: 31, txop: 188
[ 4701.352131] ath: phy4: Configure tx [queue/halq] [2/2], aifs: 3, cw_min: 31, cw_max: 1023, txop: 0
[ 4701.352303] ath: phy4: Configure tx [queue/halq] [3/3], aifs: 7, cw_min: 31, cw_max: 1023, txop: 0

Queue used by Unit 1 running an Iperf TCP Client
[ 1050.438204] ath: phy4: Enable TXE on queue: 2
[ 1050.438698] ath: phy4: Enable TXE on queue: 2
[ 1050.445629] ath: phy4: Enable TXE on queue: 2
[ 1050.445726] ath: phy4: Enable TXE on queue: 2
[ 1050.453577] ath: phy4: Enable TXE on queue: 2
[ 1050.454362] ath: phy4: Enable TXE on queue: 2
[ 1050.456088] ath: phy4: Enable TXE on queue: 2
[ 1050.460208] ath: phy4: Enable TXE on queue: 2
[ 1050.462011] ath: phy4: Enable TXE on queue: 2
[ 1050.462165] ath: phy4: Enable TXE on queue: 2
[ 1050.474008] ath: phy4: Enable TXE on queue: 2
[ 1050.474196] ath: phy4: Enable TXE on queue: 2
[ 1050.486844] ath: phy4: Enable TXE on queue: 2
[ 1050.489243] ath: phy4: Enable TXE on queue: 2
[ 1050.492391] ath: phy4: Enable TXE on queue: 2
[ 1050.494413] ath: phy4: Enable TXE on queue: 2
[ 1050.496759] ath: phy4: Enable TXE on queue: 2
[ 1050.498143] ath: phy4: Enable TXE on queue: 2
[ 1050.500533] ath: phy4: Enable TXE on queue: 2


Unit 2
[ 5557.094829] ath: phy9: Configure tx [queue/halq] [0/0], aifs: 2, cw_min: 7, cw_max: 15, txop: 102
[ 5557.094859] ath: phy9: Set queue properties for: 0
[ 5557.094881] ath: phy9: Reset TX queue: 0
[ 5557.094913] ath: phy9: Configure tx [queue/halq] [1/1], aifs: 2, cw_min: 15, cw_max: 31, txop: 188
[ 5557.094939] ath: phy9: Set queue properties for: 1
[ 5557.094957] ath: phy9: Reset TX queue: 1
[ 5557.094984] ath: phy9: Configure tx [queue/halq] [2/2], aifs: 3, cw_min: 31, cw_max: 1023, txop: 0
[ 5557.095069] ath: phy9: Set queue properties for: 2
[ 5557.095089] ath: phy9: Reset TX queue: 2
[ 5557.095119] ath: phy9: Configure tx [queue/halq] [3/3], aifs: 7, cw_min: 31, cw_max: 1023, txop: 0
[ 5557.095144] ath: phy9: Set queue properties for: 3
[ 5557.095162] ath: phy9: Reset TX queue: 3

Queue used by Unit 2 running an Iperf TCP Server
[ 6586.510412] ath: phy9: Enable TXE on queue: 2
[ 6586.510675] ath: phy9: Enable TXE on queue: 2
[ 6586.514837] ath: phy9: Enable TXE on queue: 2
[ 6586.520824] ath: phy9: Enable TXE on queue: 2
[ 6586.521071] ath: phy9: Enable TXE on queue: 2
[ 6586.527611] ath: phy9: Enable TXE on queue: 2
[ 6586.529967] ath: phy9: Enable TXE on queue: 9
[ 6586.533695] ath: phy9: Enable TXE on queue: 2
[ 6586.535674] ath: phy9: Enable TXE on queue: 2
[ 6586.550467] ath: phy9: Enable TXE on queue: 2
[ 6586.605003] ath: phy9: Enable TXE on queue: 2
[ 6586.605510] ath: phy9: Enable TXE on queue: 2
[ 6586.605752] ath: phy9: Enable TXE on queue: 2
[ 6586.609157] ath: phy9: Enable TXE on queue: 2
[ 6586.612927] ath: phy9: Enable TXE on queue: 2
[ 6586.613175] ath: phy9: Enable TXE on queue: 2
[ 6586.614441] ath: phy9: Enable TXE on queue: 2
[ 6586.617676] ath: phy9: Enable TXE on queue: 2
[ 6586.619264] ath: phy9: Enable TXE on queue: 2
[ 6586.620126] ath: phy9: Enable TXE on queue: 2
[ 6586.620440] ath: phy9: Enable TXE on queue: 2
[ 6586.627917] ath: phy9: Enable TXE on queue: 2
[ 6586.628418] ath: phy9: Enable TXE on queue: 2

Adhoc (IEEE 802.11a - channel 36)

Unit 1
[ 7481.713916] ath: phy10: Configure tx [queue/halq] [0/0], aifs: 2, cw_min: 3, cw_max: 7, txop: 47
[ 7481.713943] ath: phy10: Set queue properties for: 0
[ 7481.713961] ath: phy10: Reset TX queue: 0
[ 7481.713989] ath: phy10: Configure tx [queue/halq] [1/1], aifs: 2, cw_min: 7, cw_max: 15, txop: 94
[ 7481.714013] ath: phy10: Set queue properties for: 1
[ 7481.714031] ath: phy10: Reset TX queue: 1
[ 7481.714057] ath: phy10: Configure tx [queue/halq] [2/2], aifs: 3, cw_min: 15, cw_max: 1023, txop: 0
[ 7481.714082] ath: phy10: Set queue properties for: 2
[ 7481.714100] ath: phy10: Reset TX queue: 2
[ 7481.714118] ath: phy10: Set queue properties for: 9
[ 7481.714137] ath: phy10: Reset TX queue: 9
[ 7481.714171] ath: phy10: Configure tx [queue/halq] [3/3], aifs: 7, cw_min: 15, cw_max: 1023, txop: 0
[ 7481.714195] ath: phy10: Set queue properties for: 3
[ 7481.714214] ath: phy10: Reset TX queue: 3


Unit 2
[ 2424.793199] ath: phy9: Configure tx [queue/halq] [0/0], aifs: 2, cw_min: 3, cw_max: 7, txop: 47
[ 2424.793246] ath: phy9: Configure tx [queue/halq] [1/1], aifs: 2, cw_min: 7, cw_max: 15, txop: 94
[ 2424.793285] ath: phy9: Configure tx [queue/halq] [2/2], aifs: 3, cw_min: 15, cw_max: 1023, txop: 0
[ 2424.793338] ath: phy9: Configure tx [queue/halq] [3/3], aifs: 7, cw_min: 15, cw_max: 1023, txop: 0
________________________________________
Von: Yeoh Chun-Yeow [***@gmail.com]
Gesendet: Dienstag, 21. Oktober 2014 11:48
An: Sbeiti, Mohamad; ***@lists.open80211s.org
Betreff: Re: ath9k-based Mesh uses EDCA or DCF

Try take a look on the ath9k_conf_tx in ath9k/main.c.

The setting of aifs, cw_min , cw_max and txop may make sense to you.

----
ChunYeow

On Tue, Oct 21, 2014 at 2:38 PM, ***@tu-dortmund.de via
Devel <***@lists.open80211s.org> wrote:
> Dear all,
>
> I am wondering whether the implementation of the IEEE 802.11s in case of ath9k relies on the Enhanced Distributed Coordination Function (EDCA) to access the medium and not on the Distributed Coordination Function (DCF). Unfortunately, I could not find any information on this issue in the corresponding debugfs files of ath9k (I am running a small mesh testbed). I would greatly appreciate any hints on this topic.
>
> Best regards
> Mohamad
>
> --
> Dipl.-Ing. Mohamad Sbeiti
> Communication Networks Institute (CNI)
> Technische Universität Dortmund
> Otto-Hahn-Strasse 6
> D-44227 Dortmund, Germany
>
> Fon: +49(0)2 31/755-6128
> Fax: +49(0)2 31/755-6136
> Room: IRF 202
> http://www.kn.e-technik.tu-dortmund.de/
>
> Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender und vernichten Sie diese Mail. Vielen Dank.
> Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung eines solchen Schriftstücks per Telefax erfolgen.
>
> Important note: The information included in this e-mail is confidential. It is solely intended for the recipient. If you are not the intended recipient of this e-mail please contact the sender and delete this message. Thank you. Without prejudice of e-mail correspondence, our statements are only legally binding when they are made in the conventional written form (with personal signature) or when such documents are sent by fax.
> _______________________________________________
> Devel mailing list
> ***@lists.open80211s.org
> http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender und vernichten Sie diese Mail. Vielen Dank.
Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung eines solchen Schriftstücks per Telefax erfolgen.

Important note: The information included in this e-mail is confidential. It is solely intended for the recipient. If you are not the intended recipient of this e-mail please contact the sender and delete this message. Thank you. Without prejudice of e-mail correspondence, our statements are only legally binding when they are made in the conventional written form (with personal signature) or when such documents are sent by fax.
Loading...