ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: Need to get msdu-chaining working.
Date: Thu, 27 Feb 2014 17:18:34 -0800	[thread overview]
Message-ID: <530FE3EA.4040602@candelatech.com> (raw)
In-Reply-To: <CA+BoTQmr6+9wJ87pOmzPEBwPCMG5emfkfcUmzxXpH6gVPW+zFw@mail.gmail.com>

On 02/26/2014 10:51 PM, Michal Kazior wrote:

>>From what I understand chained msdu is a msdu that hasn't fit into the
> rx buffer and is split across the popped amsdu list. I suspect only
> the first msdu in chain has the htt_rx_desc and all other have not
> (this is what the current code does, but you'll need to verify that).
> 
> I would try to concatenate all msdus into one (lots of memcpy :( ) or
> increase the HTT_RX_BUF_SIZE so that A-MSDU frames can fit into a
> single buffer (hopefully FW/HW is capable of doing that).

I got this working, basically using memcpy approach.

Throughput is comparable what I was seeing on stock firmware,
but I do notice an issue:

The reported rx speed is almost always 6Mbps when I drive at high speeds.

(At low speeds I see rx rate reported at 1.3Gbps most of the time.)

I am pretty sure this is related to the msdu-chaining somehow.

There are lots of FIXME's in the ath10k_htt_rx_amsdu_pop method.

Any idea where the rx rate problem might lie?

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

  parent reply	other threads:[~2014-02-28  1:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26 23:38 Need to get msdu-chaining working Ben Greear
2014-02-27  6:51 ` Michal Kazior
2014-02-27 16:08   ` Ben Greear
2014-02-28  7:36     ` Michal Kazior
2014-03-03 22:13       ` Ben Greear
2014-03-04  7:36         ` Michal Kazior
2014-03-04 16:59           ` Ben Greear
2014-03-05  8:09             ` Michal Kazior
2014-03-05 20:50               ` Ben Greear
2014-03-06  7:36                 ` Michal Kazior
2014-02-28  1:18   ` Ben Greear [this message]
2014-02-28  7:41     ` Michal Kazior
2014-02-28 19:12       ` 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=530FE3EA.4040602@candelatech.com \
    --to=greearb@candelatech.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox