From: Okhwan Lee <ohlee@mwnl.snu.ac.kr>
To: ath10k@lists.infradead.org
Subject: RTS/CTS exchanges do not follow the RTS threshold
Date: Fri, 3 Oct 2014 15:08:15 +0900 [thread overview]
Message-ID: <etPan.542e3d50.19495cff.5e9@Okhwanui-Mac-mini.local> (raw)
Hi all,
As stated in the standard, if PSDU size is larger then the RTS threshold,
the PSDU follows RTS/CTS exchange.
However, based on our measurement, the RTS/CTS exchanges is decided based on the MSDU size.
If A-MPDU is aggregated with multiple 1000 byte MPDUs, the A-MPDU is transmitted without RTS/CTS even if RTS threshold is set to 2347.
Additionaly, is there any function called when RTS or CTS received in ath10k or ath? Or RTS/CTS exchange is done by the firmware?
backport version: 3.16.1
firmware version: firmware-2.bin_10.1.467.2-1
—
Okhwan Lee,
Multimedia & Wireless Networking Lab. (MWNL),
Seoul National University (SNU).
Tel: +82-2-880-1755
Cell: +82-10-4632-1980
URL: http://mwnl.snu.ac.kr/~ohlee
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next reply other threads:[~2014-10-03 6:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-03 6:08 Okhwan Lee [this message]
2014-10-03 6:14 ` RTS/CTS exchanges do not follow the RTS threshold Michal Kazior
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=etPan.542e3d50.19495cff.5e9@Okhwanui-Mac-mini.local \
--to=ohlee@mwnl.snu.ac.kr \
--cc=ath10k@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox