Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Ali MJ Al-Nasrawy <alimjalnasrawy@gmail.com>
Cc: linux-wireless@vger.kernel.org,
	Arend van Spriel <aspriel@gmail.com>,
	nbd@nbd.name
Subject: Re: mac80211 keeps trying to start ampdu session??
Date: Tue, 23 Oct 2018 22:29:32 +0200	[thread overview]
Message-ID: <7cf4a77e61aa1b48e750bb84fa12952ea648f10e.camel@sipsolutions.net> (raw)
In-Reply-To: <20181023151312.65df98c4@manjaro> (sfid-20181023_142316_161504_FE6DE0E4)

On Tue, 2018-10-23 at 15:22 +0300, Ali MJ Al-Nasrawy wrote:

> > This depends on the rate control algorithm, it triggers this.
> 
> In this case, it is minstrel_ht.
> 
> > 
> > I think - perhaps depending on the return value - mac80211 *does* give
> > up eventually, but not really sure.
> 
> The return value is handled only in
> agg-tx.c:ieee80211_tx_ba_session_handle_start and it doesn't pass it
> down or recognize difference between non-zero return values.

Indeed.

> And I don't think that it gives up retrying: I already have 800MB of
> compressed logs for the last four days only full of this message and
> additionally I ran a simple test for the last hour and found that it
> tries to start ampdu session for every frame to be sent with that TID!

Indeed, but that does seem excessive. Perhaps minstrel_ht should learn
to back off, Felix what do you think? In this case the driver basically
says "I don't want to do agg on this TID" and that repeats for every
packet.

> > Perhaps just remove the message?
> 
> OK, I report this just in case of it being unintended behavior with
> probably a negative performance impact.

It might actually, yeah ...

johannes


      reply	other threads:[~2018-10-23 20:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-23  7:44 mac80211 keeps trying to start ampdu session?? Ali MJ Al-Nasrawy
2018-10-23  8:18 ` Johannes Berg
2018-10-23 12:22   ` Ali MJ Al-Nasrawy
2018-10-23 20:29     ` Johannes Berg [this message]

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=7cf4a77e61aa1b48e750bb84fa12952ea648f10e.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=alimjalnasrawy@gmail.com \
    --cc=aspriel@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nbd@nbd.name \
    /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