ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Denton Gentry <denton.gentry@gmail.com>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: A-MSDU reception not working?
Date: Mon, 30 Jun 2014 13:28:24 -0700	[thread overview]
Message-ID: <53B1C868.9060707@candelatech.com> (raw)
In-Reply-To: <CABnBrYU3P5qXd7pE7LJ_K4JeNFLtbZnpsTgvqtpdMs07qz_gGA@mail.gmail.com>

On 06/30/2014 01:15 PM, Denton Gentry wrote:
> In iperf tests using a MacBook STA bridging through an ath10k AP to an
> Ethernet server, I'm noticing very selective packet loss. The second
> and subsequent frames in an A-MSDU packet appear to be dropped.
>
> The AP sets the A-MSDU size to 3839 bytes, and the MacBook frequently
> sends A-MSDU packets containing two TCP frames. So far as I can tell,
> the first TCP frame from an A-MSDU aggregate is delivered and the
> second is consistently lost. The MacBook generally retransmits the
> lost frame as a singleton with no aggregation, and the retransmitted
> frame makes it through.
>
> This became more noticeable after the reordering fixes in
> http://lists.infradead.org/pipermail/ath10k/2014-June/002552.html
>
> I see this A-MSDU packet loss behavior both with and without the
> reordering fixes, the first packet in an A-MSDU is delivered while the
> second is dropped. However, *without* the reordering fixes (and
> therefore with packets delivered out of order) the MacBook sends
> relatively few A-MSDU frames. *With* the reordering fixes, so all
> packets are delivered in order, the MacBook keeps sending A-MSDU and
> therefore has to deal with more packet loss. I suspect it is an
> interaction with the MacOS TCP congestion window which I'm likely
> never going to fully understand, its stuck in a region of the
> congestion window where the Wifi driver keeps choosing to using
> A-MSDU.

We saw a case where ath10k AP would drop all UDP PDUs over about 3800 bytes,
I would guess it might be the same problem.

We have not looked into the problem yet.  Stations work fine
(which is our main concern at present)...

Thanks,
Ben


-- 
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:[~2014-06-30 20:28 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-30 20:15 A-MSDU reception not working? Denton Gentry
2014-06-30 20:28 ` Ben Greear [this message]
2014-07-02 16:49 ` Michal Kazior
2014-07-04 18:58   ` Denton Gentry
2014-07-05 13:55     ` Denton Gentry
2014-07-06  2:27       ` Adrian Chadd
2014-07-07  8:30         ` Janusz Dziedzic
2014-07-07 19:26           ` Denton Gentry
2014-07-07 19:41             ` Adrian Chadd
2014-07-07 19:53               ` Denton Gentry
2014-07-08  5:58                 ` Liu CF/TW
2014-07-08  6:43             ` Janusz Dziedzic
2014-07-08  6:43             ` Denton Gentry
2014-07-08  6:50               ` Janusz Dziedzic
2014-07-08  7:02                 ` Janusz Dziedzic
2014-07-08  7:29                   ` Janusz Dziedzic
2014-07-09  6:09                     ` Denton Gentry
2014-07-09  7:39                       ` Janusz Dziedzic
2014-07-10 13:40                         ` Denton Gentry
2014-07-10 18:48                           ` Janusz Dziedzic
2014-07-11  9:20                             ` Janusz Dziedzic
2014-07-08 10:59                   ` Bartosz Markowski
2014-07-09  5:42                     ` Denton Gentry

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=53B1C868.9060707@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    --cc=denton.gentry@gmail.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