ath10k.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Krishna Chaitanya <chaitanya.mgit@gmail.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	ath10k <ath10k@lists.infradead.org>
Subject: Re: ath10k: controlling TX aggregation
Date: Fri, 12 May 2017 07:45:49 -0700	[thread overview]
Message-ID: <b830b657-3f73-de7f-d61c-1565dc14c2ef@candelatech.com> (raw)
In-Reply-To: <CABPxzY+mQ-G6PTsQV9_WVgju4bmQHwxKKW070j7v6=DDgZop4Q@mail.gmail.com>

What chipset, and what firmware version?

Thanks,
Ben

On 05/12/2017 07:43 AM, Krishna Chaitanya wrote:
> Hi,
>
> I am doing some comparative tests, wanted to configure common
> settings btw all STA's. wanted to limit agg_size to 24 in ath10k with
> the below command.
>
> echo "3 24" > /sys/kernel/debug/ieee80211/phy0/ath10k/htt_max_amsdu_ampdu
>
> The ADDBA request still has 64 and when i run iperf it is aggregating 64 frames.
>
> Except for 1 no number takes effect. If i configure 1 there is no ADDBA exchange
> initiated by ath10k.
>
> Is this expected? Can we control the aggregation size through driver?
>
> latest wireless-drivers-next and linux-firmware git is used.
>

-- 
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:[~2017-05-12 14:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-12 14:43 ath10k: controlling TX aggregation Krishna Chaitanya
2017-05-12 14:45 ` Ben Greear [this message]
2017-05-15  9:32   ` Krishna Chaitanya
2017-05-20 16:21     ` Krishna Chaitanya
2017-05-21 15:06       ` Ben Greear
2017-05-21 15:43         ` Krishna Chaitanya

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=b830b657-3f73-de7f-d61c-1565dc14c2ef@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    --cc=chaitanya.mgit@gmail.com \
    --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 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).