All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Simon Wunderlich <simon@open-mesh.com>
Cc: sven@open-mesh.com, marek@open-mesh.com, ath10k@lists.infradead.org
Subject: Re: IBSS support in ath10k - our test results and questions
Date: Fri, 20 Mar 2015 08:32:39 -0700	[thread overview]
Message-ID: <550C3D97.50307@candelatech.com> (raw)
In-Reply-To: <1799837.1jGie9QosO@prime>

On 03/20/2015 07:26 AM, Simon Wunderlich wrote:
> On Thursday 19 March 2015 14:40:42 Ben Greear wrote:
>> On 03/19/2015 10:06 AM, Simon Wunderlich wrote:
>>> [...]
>>>  * We see low throughput when communicating via IBSS between 2x ath10k or
>>>  1x
>>>
>>> ath9k + 1x ath10k (~30 MiBit/s). With HT we would have expected ~150
>>> MBit/s, with VHT even more.
>>
>> Do you see this problem with only an IBSS interface?  In other words, is my
>> firmware worse at this than stock 999.x firmware in same configuration?
> 
> Yes, we used your firmware with only one IBSS interface. And yes, in our tests 
> your firmware performed worse - with stock 999.x firmware we saw 70-90 Mbit/s, 
> which was also not great, but way better. Also in that case we saw that 
> aggregation was enabled.
> 
> The AP+IBSS concurrently was another test.
> 
> As also mentioned originally, 999.x firmware is not an option for us since we 
> will eventually need AP and IBSS at the same time.
> 
>>
>> Thanks for all the details...  Sounds like you have done more testing on
>> this than I have for sure.
> 
> We want to integrate IBSS mode into products, so we have to test thoroughly. 
> :)
> 
> If you also want to focus on IBSS, we would be happy to collaborate and test.

I am doing some work-for-hire in this area, so it's important for me to
make my firmware work as well as possible with IBSS.  For those not purchasing
support, helping to test my firmware changes and providing driver/kernel/whatever
open-source patches and help will be payment enough for me.

I'll go look to see if I can find any block-ack related code I might have missed
when porting the IBSS support forward from the 999.x firmware.

Thanks,
Ben

>>
>> In case you have a public kernel tree available somewhere with all your
>> patches, that might help speed up someone's attempt to reproduce this?
> 
> We currently don't have it. I'll ask if we can publish it. Our work was based 
> on a backports release on the mac80211 package in OpenWRT, though, so don't 
> expect a kernel tree. :)
> 
> Thanks, 
>     Simon
> 
> 
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
> 


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2015-03-20 15:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-19 17:06 IBSS support in ath10k - our test results and questions Simon Wunderlich
2015-03-19 21:40 ` Ben Greear
2015-03-20  6:44   ` Janusz Dziedzic
2015-03-20 13:56     ` Ben Greear
2015-04-07 21:17     ` Ben Greear
2015-03-20 14:26   ` Simon Wunderlich
2015-03-20 15:32     ` Ben Greear [this message]
2015-03-23 11:24   ` Sven Eckelmann
2015-04-06 17:55     ` Ben Greear
2015-04-06 20:04       ` Ben Greear
2015-04-08 18:38         ` Ben Greear
2015-04-10  2:38           ` 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=550C3D97.50307@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    --cc=marek@open-mesh.com \
    --cc=simon@open-mesh.com \
    --cc=sven@open-mesh.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.