linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "voncken" <cedric.voncken@acksys.fr>
To: "'Michal Kazior'" <michal.kazior@tieto.com>
Cc: <ath10k@lists.infradead.org>,
	"'linux-wireless'" <linux-wireless@vger.kernel.org>
Subject: RE: ath10k firmware crash
Date: Mon, 13 Oct 2014 14:06:51 +0200	[thread overview]
Message-ID: <025801cfe6de$2d4c7f70$87e57e50$@acksys.fr> (raw)
In-Reply-To: <CA+BoTQkaKXNfprRwGrQq6rKOZWvANNRrcmgU-iVdw1bONTA--w@mail.gmail.com>

> >
> > Have you a benchmark reference with ATH10K ? at this time we can send
> around 700 Mbit/s, is it the maximum or we can expected better ?
> 
> If this is OTA then this is pretty good. If this is cabled RF w/ attentuator
> it should be possible to get ~900mbps of UDP traffic with multiple streams on
> iperf. At least that's what I was getting on 10.1 firmware (on both AP and
> STA) last time I checked.
> 
> Getting more than 700mbps OTA requires AP and STA antenna alignment voodoo.
> 
I did some tests with a linksys WRT1900AC and I have ~950 mbps OTA easily.
> 
> Michał
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org More majordomo info at
> http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2014-10-13 12:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-10 14:46 ath10k firmware crash Cedric VONCKEN
2014-10-13  5:46 ` Michal Kazior
2014-10-13  7:35   ` voncken
2014-10-13  7:54     ` Michal Kazior
2014-10-13  9:20       ` voncken
2014-10-13  9:25         ` Michal Kazior
2014-10-13 12:00           ` voncken
2014-10-13 14:06           ` voncken
2014-10-13  9:23   ` voncken
2014-10-13  9:30     ` Michal Kazior
2014-10-13 12:06       ` voncken [this message]
2014-10-15 12:13         ` Bartosz Markowski
2014-10-15 13:05           ` voncken

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='025801cfe6de$2d4c7f70$87e57e50$@acksys.fr' \
    --to=cedric.voncken@acksys.fr \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=michal.kazior@tieto.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;
as well as URLs for NNTP newsgroup(s).