From: Dheryta Jaisinghani <dherytaj@iiitd.ac.in>
To: Johannes Berg <johannes@sipsolutions.net>,
make-wifi-fast@lists.bufferbloat.net,
linux-wireless <linux-wireless@vger.kernel.org>,
codel@lists.bufferbloat.net, Avery Pennarun <apenwarr@gmail.com>
Subject: [Make-wifi-fast] Fwd: Help required to understand ACK transmission and reception in ath9k
Date: Mon, 18 Apr 2016 19:08:03 +0530 [thread overview]
Message-ID: <CAB+O-6dpa5XK17dJawGEnztdciQJxPDkV5pD+JbfoKBB=WcSoA@mail.gmail.com> (raw)
In-Reply-To: <CAB+O-6fELqWua4zm4Rfae8xXWRCbLsXAeppPv4AKq6BXBZ_vxQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1144 bytes --]
---------- Forwarded message ----------
From: Dheryta Jaisinghani <dherytaj@iiitd.ac.in>
Date: Mon, Apr 18, 2016 at 6:30 PM
Subject: Help required to understand ACK transmission and reception in ath9k
To: linux-wireless@vger.kernel.org
Dear Community
I am working on ath9k driver code to understand the transmission and
reception of ack frames, sent in response to data frames.
I am not able to understand the following things:
1. Where are ACK frames generated - in the hardware or in software driver?
2. When and where in code does the driver or mac80211 decide the threshold
of ACK losses has reached and transmission should be stopped?
3. When and where in code does the driver or mac80211 decide the threshold
of frame retries has reached and transmission should be stopped?
4. Do ACK losses trigger roaming in the ath9k?
I would be very thankful if you could let me understand the above questions.
--
Thanks and Regards
Dheryta Jaisinghani
PhD Scholar
MUC Research Group
IIIT-Delhi
URL:http://www.dheryta.co.in
--
Thanks and Regards
Dheryta Jaisinghani
PhD Scholar
MUC Research Group
IIIT-Delhi
URL:http://www.dheryta.co.in
[-- Attachment #2: Type: text/html, Size: 1906 bytes --]
parent reply other threads:[~2016-04-18 13:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAB+O-6fELqWua4zm4Rfae8xXWRCbLsXAeppPv4AKq6BXBZ_vxQ@mail.gmail.com>]
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
List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAB+O-6dpa5XK17dJawGEnztdciQJxPDkV5pD+JbfoKBB=WcSoA@mail.gmail.com' \
--to=dherytaj@iiitd.ac.in \
--cc=apenwarr@gmail.com \
--cc=codel@lists.bufferbloat.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=make-wifi-fast@lists.bufferbloat.net \
/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