ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Wunderlich <simon@open-mesh.com>
To: Ben Greear <greearb@candelatech.com>
Cc: sven@open-mesh.com, marek@open-mesh.com, ath10k@lists.infradead.org
Subject: Re: Re: IBSS support in ath10k - our test results and questions
Date: Fri, 20 Mar 2015 15:26:21 +0100	[thread overview]
Message-ID: <1799837.1jGie9QosO@prime> (raw)
In-Reply-To: <550B425A.7090505@candelatech.com>

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.

> 
> 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

  parent reply	other threads:[~2015-03-20 14:29 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 [this message]
2015-03-20 15:32     ` Ben Greear
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=1799837.1jGie9QosO@prime \
    --to=simon@open-mesh.com \
    --cc=ath10k@lists.infradead.org \
    --cc=greearb@candelatech.com \
    --cc=marek@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox