From: Hannes Harms <hannes.harms@tu-bs.de>
To: ath10k@lists.infradead.org
Subject: Re: ath10k IBSS and A-MSDU throuput
Date: Fri, 29 Apr 2016 19:01:42 +0200 [thread overview]
Message-ID: <57239376.2090701@tu-bs.de> (raw)
In-Reply-To: <572389ED.6080306@candelatech.com>
To sniff frames on air I would need additional hardware, right?
Or maybe there is a possibility to debug in / outgoing amsdu frames in
the ath10k driver?
Unfortunately my kernel programming skills are very limited,
but maybe I will continue testing next week.
Thanks,
Hannes
Am 29.04.2016 um 18:21 schrieb Ben Greear:
>
>
> On 04/29/2016 08:51 AM, Harms, Hannes wrote:
>> Hi everyone,
>>
>> I have set up two Compex WLE900 in ad-hoc mode, 80MHz channel width,
>> channel 100.
>> I am using kernel 3.17 from Gateworks for imx6 and
>> my own compat_wirless (4.4.2) with all patches from Candela for
>> ath10k and all patches for mac80211 from the
>> Candela 4.4 kernel tree.
>>
>> The upload for TCP is about 200 MBit/s and the download is about 250
>> MBit/s, tested with iperf3.
>>
>> Now I am trying to enable A-MSDU as described in the firmware release
>> 10.1.467-ct-15 from Candela,
>> but I can not measure anydifference in throughput.
>>
>> Could anyone confirm that A-MSDU is really working with IBSS?
>
> You can sniff it and see if you can sniff amsdu frames on air?
>
> I only tested it a bit when developing that feature for another user
> (who eventually decided to not use it anyway since it required linux
> kernel hacks to make it work), so possibly there was a regression...
>
> Thanks,
> Ben
>
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-04-29 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 15:51 ath10k IBSS and A-MSDU throuput Harms, Hannes
2016-04-29 16:21 ` Ben Greear
2016-04-29 17:01 ` Hannes Harms [this message]
2016-04-29 19:24 ` Ben Greear
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=57239376.2090701@tu-bs.de \
--to=hannes.harms@tu-bs.de \
--cc=ath10k@lists.infradead.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