linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Helmut Schaa <helmut.schaa@googlemail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
	Dan Williams <dcbw@redhat.com>,
	"linux-wireless" <linux-wireless@vger.kernel.org>,
	Aeolus.Yang@atheros.com,
	Senthil Balasubramanian <senthilkumar@atheros.com>,
	Gaurav.Jauhar@atheros.com, David Miller <davem@davemloft.net>,
	Jouni Malinen <j@w1.fi>
Subject: Re: Scan while TX/RX'ing a lot of data
Date: Wed, 20 May 2009 13:41:46 +0200	[thread overview]
Message-ID: <200905201341.47185.helmut.schaa@gmail.com> (raw)
In-Reply-To: <1242724000.17164.10.camel@johannes.local>

Am Dienstag, 19. Mai 2009 schrieb Johannes Berg:
> On Mon, 2009-05-18 at 15:43 +0200, Helmut Schaa wrote:

> > One solution would be to force all drivers to report the tx status. Another
> > one would be to just wait until the device's queue is empty. At that point
> > we know that all pending data frames were sent out and additionally the
> > nullfunc frame was also sent out, so we can safely switch to the next
> > to-be-scanned channel.
> 
> Some drivers now flush queues at channel switch time, but there's no way
> to guarantee that the software queues are actually empty and the
> nullfunc frame isn't queued up behind other traffic. Also, waiting for
> any driver to report a status will lead to problems because the driver
> might just have dropped the frame for various reasons like being out of
> memory.

Hmm, the problem is basically (from a mac80211 perspective) that the
mdev tx queue could still contain data frames when the nullfunc frame
gets queued, right? And we do not assure that these frames are sent
out before the channel switch.

Hence, would it be possible to:
1) Stop all sub_if tx queues (afterwards no new data frames should
   appear in the mdev tx queue)
2) Queue the nullfunc frame
3) Flush the mdev's tx queue
4) Switch the channel
?

Helmut

  reply	other threads:[~2009-05-20 11:41 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-14 17:52 Scan while TX/RX'ing a lot of data Luis R. Rodriguez
2009-05-14 18:54 ` Dan Williams
2009-05-14 19:06   ` Johannes Berg
2009-05-14 20:50     ` Dan Williams
2009-05-14 20:53       ` Johannes Berg
2009-05-14 19:07   ` Luis R. Rodriguez
2009-05-14 20:57     ` Dan Williams
2009-05-14 21:26       ` Luis R. Rodriguez
2009-05-14 22:17         ` Luis R. Rodriguez
2009-05-16  6:12         ` Luis R. Rodriguez
2009-05-16  6:15           ` Luis R. Rodriguez
2009-05-16 12:57           ` Johannes Berg
2009-05-18 12:38             ` John W. Linville
2009-05-18 17:52               ` Luis R. Rodriguez
2009-05-18 13:43             ` Helmut Schaa
2009-05-19  9:06               ` Johannes Berg
2009-05-20 11:41                 ` Helmut Schaa [this message]
2009-05-20 11:44                   ` Johannes Berg
2009-05-20 13:43                     ` Helmut Schaa
2009-05-20 13:53                       ` Johannes Berg
2009-05-18 18:06             ` Luis R. Rodriguez
2009-05-19  9:09               ` Johannes Berg
2009-05-15  8:11   ` Holger Schurig
2009-05-15  8:31     ` Johannes Berg
2009-05-15 23:15     ` Dan Williams
2009-05-16 12:48       ` Johannes Berg
2009-05-18 15:35         ` Dan Williams

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=200905201341.47185.helmut.schaa@gmail.com \
    --to=helmut.schaa@googlemail.com \
    --cc=Aeolus.Yang@atheros.com \
    --cc=Gaurav.Jauhar@atheros.com \
    --cc=davem@davemloft.net \
    --cc=dcbw@redhat.com \
    --cc=j@w1.fi \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    --cc=senthilkumar@atheros.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;
as well as URLs for NNTP newsgroup(s).