From: Olivier Marce <Olivier.Marce@alcatel-lucent.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Ack and Block Ack processing
Date: Mon, 10 Feb 2014 11:11:30 +0100 [thread overview]
Message-ID: <52F8A5D2.9050608@alcatel-lucent.com> (raw)
In-Reply-To: <CADxDmp7+K4eQBCSi35_p16qaaqs72TD89Wnx46+4TuVrOCm=oA@mail.gmail.com>
Hi Kamram,
thanks, this is a useful information indeed.
But my question was about to get notified of the details of exchange
between emitter and transmitter. E.g. how many retries have been needed
to get the a MPDU to be acked.
On 10/02/2014 10:45, Kamran Nishat wrote:
> as Adrian said we got information received in a BlockACK
> (ath_tx_complete_aggr in xmit.c)
> you get a bitmap, SSN and retires done for AMPDU.
>
>
>
> On Mon, Feb 10, 2014 at 1:57 PM, Olivier Marce
> <Olivier.Marce@alcatel-lucent.com
> <mailto:Olivier.Marce@alcatel-lucent.com>> wrote:
>
> Thanks for the quick and precise answer.
>
> Then, I wonder is there is a way to be notified of sending/receiving of
> frames by the HW. For example, can we be notified of ACK (or BA)
> received and processed by the HW, or by frame retransmited by the HW ?
>
> Thanks
>
> On 03/02/2014 17:29, Adrian Chadd wrote:
> > Hi,
> >
> > So on the Atheros NICs, the block-acks are generated by the receiver
> > in hardware and processed by the transmitter in hardware; you
> then get
> > a bitmap in the TX completion descriptor telling you which frames did
> > succeed/fail.
> >
> > The TX completion path does check the two 32 bit blockack (ba) fields
> > in the TX descriptor for completion. It doesn't hand-parse a BA
> frame.
> >
> >
> > -a
> >
> >
> > On 3 February 2014 07:48, Olivier Marce
> > <Olivier.Marce@alcatel-lucent.com
> <mailto:Olivier.Marce@alcatel-lucent.com>> wrote:
> >> Hi everybody,
> >> thanks to all of you who share your knowledge and expertise on
> ath9k.
> >>
> >> I wonder if Ack and Block Ack are processed directly by the HW on
> >> receipt and not the firmware.
> >>
> >> There are several messages that confirm that Ack and Block Ack are
> >> *sent* by HW
> (http://www.spinics.net/lists/linux-wireless/msg106950.html)
> >> But are they processed (on receipt) also by HW ? I analysed firmware
> >> code and I did not find any Ack/BA processing.
> >>
> >> Is my understanding correct ?
> >>
> >> Best regards
> >>
> >>
> >> --
> >> Olivier Marc?
> >> Alcatel-Lucent Bell Labs France
> >> _______________________________________________
> >> ath9k-devel mailing list
> >> ath9k-devel at lists.ath9k.org <mailto:ath9k-devel@lists.ath9k.org>
> >> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
> >
> >
>
> --
> Olivier Marc?
> Alcatel-Lucent Bell Labs France
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org <mailto:ath9k-devel@lists.ath9k.org>
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
>
--
Olivier Marc?
Alcatel-Lucent Bell Labs France
next prev parent reply other threads:[~2014-02-10 10:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 15:48 [ath9k-devel] Ack and Block Ack processing Olivier Marce
2014-02-03 16:29 ` Adrian Chadd
2014-02-10 8:57 ` Olivier Marce
2014-02-10 9:45 ` Kamran Nishat
2014-02-10 10:11 ` Olivier Marce [this message]
2014-02-10 18:02 ` abhinav narain
2014-02-03 17:01 ` abhinav narain
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=52F8A5D2.9050608@alcatel-lucent.com \
--to=olivier.marce@alcatel-lucent.com \
--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.