From: "Arend van Spriel" <arend@broadcom.com>
To: Matteo <matteo.danieletto@gmail.com>
Cc: brcm80211-dev-list@broadcom.com,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [bcmdhd] Retransmission packet
Date: Wed, 5 Jun 2013 15:28:10 +0200 [thread overview]
Message-ID: <51AF3CEA.1000409@broadcom.com> (raw)
In-Reply-To: <7CCB4989-196D-421E-BE73-1EF52F25C381@gmail.com>
+ linux-wireless
On 06/05/2013 02:04 PM, Matteo wrote:
> Hi Arend,
> thank a lot.
>
> yea, I wanted to find the retransmissions of the frame over the air.
> I don't know, if other devices (broadcom or atheros) could give that information.
On Android? I guess any mac80211 based driver could give you that
information. The information is provided by the driver to mac80211 upon
txstatus using struct ieee80211_tx_info::status. The rates field should
contain the rates at which the transmits were attempted and how often
(see explanation of struct ieee80211_tx_rate).
Regards,
Arend
> Thanks again
> Matteo
>
> On Jun 5, 2013, at 10:50 AM, "Arend van Spriel" <arend@broadcom.com> wrote:
>
>> - linux-wireless@vger.kernel.org
>>
>> bcmdhd is not an upstream linux driver so removing that mailing list address.
>>
>> On 06/04/2013 11:20 PM, Matteo Danieletto wrote:
>>> Hi all,
>>>
>>> I am trying to extract the number of retransmissions frame occur during
>>> data transfer between two nodes.
>>
>> I suppose you want the know the retransmissions of the frame over the air. The retries in the code below are over the bus between host and device. So that is not the information you want (right?).
>>
>> The bad news is that the information is not available in the driver.
>>
>> Regards,
>> Arend
>>
>>> I found in did_sdio.c this function:
>>>
>>> 1. /* Writes a HW/SW header into the packet and sends it. */
>>> 2. /* Assumes: (a) header space already there, (b) caller holds lock */
>>> 3. staticint
>>> 4. dhdsdio_txpkt(dhd_bus_t *bus,void*pkt,uint chan,boolfree_pkt)
>>>
>>>
>>> .
>>> .
>>> .
>>> there is this part:
>>>
>>> 1. do{
>>> 2. ret
>>> =dhd_bcmsdh_send_buf(bus,bcmsdh_cur_sbwad(sdh),SDIO_FUNC_2,F2SYNC,
>>> 3. frame,len,pkt,NULL,NULL);
>>> 4. bus->f2txdata++;
>>> 5. ASSERT(ret !=BCME_PENDING);
>>> 6.
>>>
>>> 7. if(ret <0){
>>> 8. /* On failure, abort the command and terminate the frame */
>>> 9. DHD_INFO(("%s: sdio error %d, abort command
>>> and terminate frame.\n",
>>> 10. __FUNCTION__,ret));
>>> 11. bus->tx_sderrs++;
>>> 12.
>>>
>>> 13. bcmsdh_abort(sdh,SDIO_FUNC_2);
>>> 14.
>>> bcmsdh_cfg_write(sdh,SDIO_FUNC_1,SBSDIO_FUNC1_FRAMECTRL,
>>> 15. SFC_WF_TERM,NULL);
>>> 16. bus->f1regdata++;
>>> 17.
>>>
>>> 18. for(i =0;i <3;i++){
>>> 19. uint8 hi,lo;
>>> 20. hi =bcmsdh_cfg_read(sdh,SDIO_FUNC_1,
>>> 21.
>>> SBSDIO_FUNC1_WFRAMEBCHI,NULL);
>>> 22. lo =bcmsdh_cfg_read(sdh,SDIO_FUNC_1,
>>> 23.
>>> SBSDIO_FUNC1_WFRAMEBCLO,NULL);
>>> 24. bus->f1regdata +=2;
>>> 25. if((hi ==0)&&(lo ==0))
>>> 26. break;
>>> 27. }
>>> 28.
>>>
>>> 29. }
>>> 30. if(ret ==0){
>>> 31. bus->tx_seq =(bus->tx_seq
>>> +1)%SDPCM_SEQUENCE_WRAP;
>>> 32. }
>>> 33. }while((ret <0)&&retrydata &&retries++<TXRETRIES);
>>>
>>>
>>>
>>> I exploited iperf to create a data stream between two nodes, but it
>>> never occurred an incrementation of retries variable, then everytime
>>> did_bcmsdh_send_buf returned 0.
>>>
>>> So, I don't know if it is the right point to extract this information
>>> and it never occurred a retransmission, or more it is not possible
>>> extract what I want.
>>>
>>> Thanks a lot
>>>
>>> Matteo
>>>
>>>
>>
>>
>
>
next parent reply other threads:[~2013-06-05 13:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <92D01B34-EB7E-47BA-ABD1-1C85B366ED47@gmail.com>
[not found] ` <51AEFBD6.3000100@broadcom.com>
[not found] ` <7CCB4989-196D-421E-BE73-1EF52F25C381@gmail.com>
2013-06-05 13:28 ` Arend van Spriel [this message]
2013-06-05 20:21 ` [bcmdhd] Retransmission packet Matteo
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=51AF3CEA.1000409@broadcom.com \
--to=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=matteo.danieletto@gmail.com \
/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.