From: Michael Krupp <michaelkrupp@gmx.net>
To: michal.kazior@tieto.com
Cc: ath10k@lists.infradead.org
Subject: Re: Support for QCA6174 [168c:003e]
Date: Tue, 27 Oct 2015 13:01:20 +0100 [thread overview]
Message-ID: <562F6790.8070601@gmx.net> (raw)
In-Reply-To: <CA+BoTQ=zyC4aGW+1HNG7d7Ae3yr6SCdt6YRYQ9rhK7iqokYMCg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 965 bytes --]
Hello Michał,
thank you for pointing me to those discussions.
I will repeat my tests using iperf to also cover UDP, and will also try some
older kernel releases, pre-dating 3.19. Also I'll try another AP as mentioned
earlier.
Michael
On 10/27/2015 12:27 PM, Michal Kazior wrote:
> On 27 October 2015 at 12:22, Michael Krupp <michaelkrupp@gmx.net> wrote:
>> Hello Michał
>>
>> yes, I checked the actual performance via netcat, scp and rsync. I'll report
>> back once I have tested against another AP.
>
> TCP performance is known to be tricky/poor in various scenarios. There
> were some discussions in the past:
>
> - http://lists.infradead.org/pipermail/ath10k/2015-October/006160.html
> - http://thread.gmane.org/gmane.linux.network/348420
>
>
> Michał
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
>
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 146 bytes --]
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2015-10-27 12:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-25 3:57 Support for QCA6174 [168c:003e] Michael Krupp
2015-10-26 7:20 ` Michal Kazior
2015-10-26 21:18 ` Michael Krupp
2015-10-27 6:22 ` Michal Kazior
2015-10-27 11:22 ` Michael Krupp
2015-10-27 11:27 ` Michal Kazior
2015-10-27 12:01 ` Michael Krupp [this message]
2015-10-29 20:44 ` Michael Krupp
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=562F6790.8070601@gmx.net \
--to=michaelkrupp@gmx.net \
--cc=ath10k@lists.infradead.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 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.