All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Klaus Kinski <jpo234@outlook.de>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Packet throughput (and those iperf data rate) with mac80211/ath9k is 20% worse than net80211/madwifi
Date: Mon, 30 Jan 2017 17:17:52 +0100	[thread overview]
Message-ID: <87lgtsjz6o.fsf@toke.dk> (raw)
In-Reply-To: <HE1PR0701MB1803E46BC8EC38D682361523FC4B0@HE1PR0701MB1803.eurprd07.prod.outlook.com> (Klaus Kinski's message of "Mon, 30 Jan 2017 15:57:08 +0000")

Klaus Kinski <jpo234-1ViLX0X+lBKELgA04lAiVw@public.gmane.org> writes:

> Hello all,
>
> this is a blast from the past, but something that still bothers me.
> I have two systems with Atheros/QCA cards:
>
> System A:
>   OS and driver: Linux 3.18.36 with last Madwifi/sample code from trunk
>
>   WLAN card: AR5413 (Senao EMP-8602 PLUS-S)
>
> System B:
>   OS and driver: Linux 3.18.36 with mac80211/minstrel and ath9k from backports-4.2
>
>   WLAN card: AR9280 (Compex WLE200NX)
>
> While doing the performance measurements both systems are connected to a reference system
>
> with a HF cable, so there should be no outside influences.
>
> Both systems are running in 802.11a mode on channel 40.
> The following table shows 802.11 data packets sent from system A and B generated by
>
> iperf in UDP mode over a 2s interval:

What version of iperf, and configured to which rate? Some versions of
iperf will send its traffic in very large bursts (see
http://burntchrome.blogspot.se/2016/09/iperf3-and-microbursts.html?m=1)
which could cause the queue inside ath9k to overflow (it is only 123
packets pre-4.10).

Did you try the latest mac80211/ath9k from 4.10? The queueing structure
changed dramatically, which would impact this, at least if it's a queue
overflow problem...

-Toke

  reply	other threads:[~2017-01-30 16:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-30 15:57 Packet throughput (and those iperf data rate) with mac80211/ath9k is 20% worse than net80211/madwifi Klaus Kinski
2017-01-30 16:17 ` Toke Høiland-Jørgensen [this message]
2017-01-30 16:49   ` Dave Taht
     [not found]     ` <HE1PR0701MB1803A03DD96F300119936D0EFC4B0@HE1PR0701MB1803.eurprd07.prod.outlook.com>
2017-01-30 19:43       ` Toke Høiland-Jørgensen
2017-01-31  7:54         ` Wojciech Dubowik
     [not found]           ` <HE1PR0701MB18031C6DF4DF46865EBF9E87FC4A0@HE1PR0701MB1803.eurprd07.prod.outlook.com>
     [not found]             ` <f5adadba-2764-a7cc-c661-7061545341a7@neratec.com>
     [not found]               ` <HE1PR0701MB1803911A9D8B8CF7813C6EACFC4A0@HE1PR0701MB1803.eurprd07.prod.outlook.com>
2017-01-31  9:42                 ` Wojciech Dubowik
     [not found]               ` <CAEvAWuGa6YSFA80mC0+saoGO5VWGNqfbyw94Nv0vfhSoQfD-Jw@mail.gmail.com>
     [not found]                 ` <HE1PR0701MB1803B7D5D0182EF7DD662B18FC4A0@HE1PR0701MB1803.eurprd07.prod.outlook.com>
2017-01-31  9:52                   ` Wojciech Dubowik
2017-01-31 12:42                     ` Rafał Miłecki
2017-01-31 15:26                     ` 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=87lgtsjz6o.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=jpo234@outlook.de \
    --cc=linux-wireless@vger.kernel.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 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.