All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: wireless <linux-wireless@vger.kernel.org>,
	Jouni Malinen <j@w1.fi>,
	Christian Lamparter <chunkeey@googlemail.com>
Subject: Re: [RFC] mac80211: fix release_reorder_timeout in scan
Date: Mon, 27 Sep 2010 20:54:29 +0200	[thread overview]
Message-ID: <1285613669.4043.27.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <AANLkTin+1-_RA8fY8B5-omQi3kMJ3U0iw8Kdg=FC2rnP@mail.gmail.com>

On Mon, 2010-09-27 at 11:49 -0700, Luis R. Rodriguez wrote:

> >> I don't get what we are doing with these frames today, are you saying
> >> we pegged some of these frames into the reorder buffer when starting a
> >> sw scan, or that we were dropping them?

> yeah, I was thinking about the release reorder buffer and its
> respective timeout, I thought that's what the subject of this patch
> was about.

So I got confused by your question ...

We put them into the reorder buffer, but if we get a reorder timeout
while scanning we'll drop the frames which isn't necessary.

johannes


  reply	other threads:[~2010-09-27 18:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-23 18:27 [RFC] mac80211: fix release_reorder_timeout in scan Johannes Berg
2010-09-27 18:14 ` Luis R. Rodriguez
2010-09-27 18:20   ` Johannes Berg
2010-09-27 18:49     ` Luis R. Rodriguez
2010-09-27 18:54       ` Johannes Berg [this message]
2010-09-27 19:03         ` Luis R. Rodriguez
2010-09-27 19:06           ` Johannes Berg
2010-09-27 19:09             ` Luis R. Rodriguez
2010-09-27 19:10               ` Johannes Berg
2010-09-27 19:12                 ` Luis R. Rodriguez
2010-09-27 22:34                   ` Matt Smith
2010-10-05 23:07                     ` [ath9k-devel] " Luis R. Rodriguez
2010-10-05 23:07                       ` Luis R. Rodriguez

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=1285613669.4043.27.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=chunkeey@googlemail.com \
    --cc=j@w1.fi \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@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 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.