From: Ali Abedi <a2abedi@uwaterloo.ca>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] The operation of Minstrel_ht
Date: Mon, 03 Nov 2014 11:39:03 -0500 [thread overview]
Message-ID: <5457AFA7.7020108@mailservices.uwaterloo.ca> (raw)
In-Reply-To: <CABiX5j-AxnVV51cc9+uWp8wBencR3u7kX_Sjc-FkNBEwd+f2+w@mail.gmail.com>
Thank you for your reply.
Regarding number 1, does MRR used when no blockack is received?
Because I believe transmission is done when the blockack is received
even if most of the MPDUs are lost.
Thanks,
Ali
On 14-10-31 08:04 PM, Kevin Hayes wrote:
> 1. multirate retry is still available for HT aggregates yes.
> 2. You would just set the number of retries to 0. Then if the
> aggregate failed (either partially or completely) it would be up to SW
> to do something.
> 3. Software retry is not defined by the spec, but rather by
> implementation.
> Retries of MPDU's are done by SW in every case except for the case
> where the BA never came back, as you said.
>
>
>
> On Fri, Oct 10, 2014 at 7:40 AM, Ali Abedi <a2abedi@uwaterloo.ca
> <mailto:a2abedi@uwaterloo.ca>> wrote:
>
> Hello,
>
>
> I have a few questions about the operation of Minstrel_ht. I couldn't
> find a good reference that
> explains minstrel_ht. I tried to understand it by reading the
> code. The
> fact that frame aggregation
> was added to the picture confuses me a bit. I understand the multirate
> retry chain in Minstrel (802.11g).
>
> 1- Since the hardware only reties the frame when no block ack is
> received (phy header damage)
> (is this correct?), do we still use the multirate retry chain with
> frame
> aggregation?
>
> 2- Is it possible to disable hardware retries?
>
> 3- Is software retry defined for an individual MPDU? Is this the
> number
> of times an MPDU
> is rescheduled for transmission?
>
>
> Thank you in advance.
>
> Best,
> Ali
>
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org <mailto:ath9k-devel@lists.ath9k.org>
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
>
>
>
> --
> Kevin Hayes
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20141103/38dde532/attachment.htm
next prev parent reply other threads:[~2014-11-03 16:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 14:40 [ath9k-devel] The operation of Minstrel_ht Ali Abedi
2014-11-01 0:04 ` Kevin Hayes
2014-11-03 16:39 ` Ali Abedi [this message]
2014-11-04 4:10 ` Kevin Hayes
-- strict thread matches above, loose matches on Subject: below --
2014-11-04 4:48 Bonzar
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=5457AFA7.7020108@mailservices.uwaterloo.ca \
--to=a2abedi@uwaterloo.ca \
--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.