From: Claudio Pisa <claudio.pisa@uniroma2.it>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] txop bursts issues
Date: Thu, 24 May 2012 16:14:58 +0100 [thread overview]
Message-ID: <4FBE5072.7070100@uniroma2.it> (raw)
Hello, everybody.
I am working on a research project that uses the txop mechanism to
distinguish, on a 802.11b/g STA, between packet losses caused by
collisions and by noise.
I found some issues that are not clear to me on both mac80211 and ath9k,
but hopefully you can help.
The first one is the motivation behind commit
133a3ff2c934223a8143bfa52401bba962a97165, "cfg80211: allow setting TXQ
parameters only in AP mode". Is this just a temporary fix?
To get around this, and activate the txop functionality on a STA, I am
just hardcoding the burstTime (qi.tqi_burstTime = 102;) inside the
ath_txq_setup function in drivers/net/wireless/ath/ath9k/xmit.c
Then: is the duration field set by the hardware? We are using a D-Link
AR5008 NIC. It seems like the driver is always setting the duration to 0
due to (what I think is) a bug in net/mac80211/tx.c (line 154 function
ieee80211_duration):
/* Don't calculate ACKs for QoS Frames with NoAck Policy set */
if (ieee80211_is_data_qos(hdr->frame_control) &&
*(ieee80211_get_qos_ctl(hdr)) |
IEEE80211_QOS_CTL_ACK_POLICY_NOACK)
dur = 0;
(i.e. using a bitwise or instead of a bitwise and) but then, sniffing
the frames, we find that the duration field is always set. However, this
duration field value seems not to be covering the subsequent ack and
transmission.
So I am wondering: is txop supported in ath9k? Or am I just doing
something wrong?
thank you and all the best,
Claudio
next reply other threads:[~2012-05-24 15:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 15:14 Claudio Pisa [this message]
2012-05-30 9:16 ` [ath9k-devel] txop bursts issues Claudio Pisa
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=4FBE5072.7070100@uniroma2.it \
--to=claudio.pisa@uniroma2.it \
--cc=ath9k-devel@lists.ath9k.org \
/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.