All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@openwrt.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, linville@tuxdriver.com,
	Helmut Schaa <helmut.schaa@googlemail.com>
Subject: Re: [PATCH] mac80211: retry sending failed BAR frames later instead of tearing down aggr
Date: Wed, 31 Aug 2011 16:47:03 +0200	[thread overview]
Message-ID: <4E5E4967.8070401@openwrt.org> (raw)
In-Reply-To: <1314792948.4161.23.camel@jlt3.sipsolutions.net>

On 2011-08-31 2:15 PM, Johannes Berg wrote:
> On Sun, 2011-08-28 at 21:11 +0200, Felix Fietkau wrote:
>>  Unfortunately failed BAR tx attempts happen more frequently than I
>>  expected, and the resulting aggregation teardowns cause performance
>>  issues, as the aggregation session does not always get re-established
>>  properly.
>
> I find this curious. How can tons of traffic go through, but BAR frames
> fail? These are unicast and should be retried a bunch...
I think it mostly happens when the client goes to powersave (triggered 
by background scans, etc).

>>  Instead of tearing down the entire aggr session, we can simply store the
>>  SSN of the last failed BAR tx attempt, wait for the first successful
>>  tx status event, and then send another BAR with the same SSN.
>
> So what if it keeps failing? I think eventually we'd want to kill the
> session?
If it keeps failing, then the connection is probably so bad that it 
doesn't matter if we kill the session or not.

- Felix

  parent reply	other threads:[~2011-08-31 14:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-28 19:11 [PATCH] mac80211: retry sending failed BAR frames later instead of tearing down aggr Felix Fietkau
2011-08-29  6:58 ` Helmut Schaa
2011-08-29  7:05   ` Felix Fietkau
2011-08-31 12:15 ` Johannes Berg
2011-08-31 12:31   ` Helmut Schaa
2011-08-31 14:47     ` Felix Fietkau
2011-08-31 14:47   ` Felix Fietkau [this message]
2011-08-31 17:11     ` Johannes Berg

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=4E5E4967.8070401@openwrt.org \
    --to=nbd@openwrt.org \
    --cc=helmut.schaa@googlemail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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 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.