From: Adrian Chadd <adrian@freebsd.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k monitor mode injection packet delay
Date: Tue, 28 Jun 2016 19:46:18 -0700 [thread overview]
Message-ID: <CAJ-VmonG3pR61fCb-XswrxFO+ge=cfBtMfKLoMNsGG6DP2EOnA@mail.gmail.com> (raw)
In-Reply-To: <6d0f8803.398a.15599e721ba.Coremail.caesargo@163.com>
hi!
ok. 1ms is a long amount of time. Maybe use the tracing feature in
ath9k and/or add some debugging in the RX and TX paths that log the
TSC (system clock) value whenever the RX path and TX queue path fires?
See if it's scheduling things to the hardware quickly or not. It may
be something really silly like context switching between the RX and TX
threads of the driver.
-adrian
On 28 June 2016 at 19:05, Cesar <caesargo@163.com> wrote:
> Dear Adrian Chadd,
>
> Thanks for your reply. It's correct that USB may introduce some delays, but
> in our experiment we use mini-pcie devices indeed...
>
> Cesar
>
>
>
>
>
>
>
> At 2016-06-29 04:05:32, "Adrian Chadd" <adrian@freebsd.org> wrote:
>>Hi,
>>
>>can you try this using pci/pcie devices instead of USB? There may be
>>USB scheduling things in the way.
>>
>>On 27 June 2016 at 20:55, Cesar <caesargo@163.com> wrote:
>>> Hello all,
>>> We?ve recently tried to test packet injection performace in ath9k monitor
>>> mode. We set 2 laptops in monitor mode , PC 1 send a 500 Byte packets
>>> out,
>>> and PC 2 return a 500 Bytes packet back at once when it receives the
>>> packet
>>> of PC 1. Then we measured the RTT time and found it's about 1000us !!!
>>>
>>> Test environment:
>>> NIC: AR9287
>>> driver: ath9k
>>> system: ubuntu 14.04 with kernel 3.14.57
>>> send rate : at a fixed rate 54Mb
>>>
>>>
>>> We tried to send packets as "low" as possible in driver stack, and we're
>>> sure that we disabled the CCA and backoff using flags below:
>>>
>>> AR_DIAG_FORCE_CH_IDLE_HIGH
>>> AR_DIAG_IGNORE_VIRT_CS
>>> AR_D_GBL_IFS_MISC_IGNORE_BACKOFF
>>>
>>> besides we change the aifs to 1 and cwmin cwmax to 0 in ath_txq_setup to
>>> ensure there's no backoff. we even put our laptaps to a underground
>>> garage
>>> where channel is almost clean.But the test results is still about
>>> 1000us....
>>>
>>> We've been stucked for serveral months, Any suggestion?
>>> Any feedback welcome...
>>> Thnkz in advance!!!
>>>
>>> Cesar
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> ath9k-devel mailing list
>>> ath9k-devel at lists.ath9k.org
>>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>>>
>
>
>
>
next prev parent reply other threads:[~2016-06-29 2:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 3:55 [ath9k-devel] ath9k monitor mode injection packet delay Cesar
2016-06-28 20:05 ` Adrian Chadd
2016-06-29 2:05 ` Cesar
2016-06-29 2:46 ` Adrian Chadd [this message]
2016-07-05 11:24 ` Cesar
2016-07-06 15:18 ` Adrian Chadd
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='CAJ-VmonG3pR61fCb-XswrxFO+ge=cfBtMfKLoMNsGG6DP2EOnA@mail.gmail.com' \
--to=adrian@freebsd.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).