From: Michael Buesch <mb@bu3sch.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Ulrich Kunitz <kune@deine-taler.de>,
Daniel Drake <dsd@gentoo.org>,
linux-wireless@vger.kernel.org
Subject: Re: [RFC 2/2] mac80211: revamp interface and filter configuration
Date: Wed, 5 Sep 2007 16:16:24 +0200 [thread overview]
Message-ID: <200709051616.25044.mb@bu3sch.de> (raw)
In-Reply-To: <1188991396.9942.97.camel@johannes.berg>
On Wednesday 05 September 2007, Johannes Berg wrote:
> On Wed, 2007-09-05 at 07:16 +0200, Ulrich Kunitz wrote:
>
> > I see three options to achieve this:
> >
> > 1) Use ieee80211_stop_queues() in ->configure_filter() and
> > ieee80211_wake_queues() at the end of the workqueue function.
> >
> > 2) Throw away all packets until the workqueue function
> > terminates.
> >
> > 3) Implement our own tx queue.
> >
> > I prefer to do option (1) because it wouldn't require adding
> > additional fields to our private structure beside the work_struct
> > for the workqueue function, it is simple to implement and it would
> > not throw away any packets. Are there any side effects that I have
> > overlooked?
>
> I think Michael says it's currently buggy if called outside of ->tx().
Yes, we had a bug in b43 where we used it in the periodic workqueue.
It causes really hard to track down system freezes on UP
systems due to races with the TX code.
It will hang and busy wait in the qdisc code when this triggers.
I didn't see a fix for this, yet.
But I think a fix could probably be to take the netif_tx_lock
in the ieee80211_stop_queues() function, so we make sure that no
TX is in progress while we stop it.
next prev parent reply other threads:[~2007-09-05 14:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-21 16:18 [RFC 0/2] the filter stuff again Johannes Berg
2007-08-21 16:18 ` [RFC 1/2] mac80211: allow drivers to indicate failed FCS/PLCP checksum Johannes Berg
2007-08-21 21:07 ` Ivo van Doorn
2007-08-22 9:22 ` Johannes Berg
2007-08-22 19:11 ` Ivo van Doorn
2007-08-23 14:13 ` Johannes Berg
2007-08-21 16:18 ` [RFC 2/2] mac80211: revamp interface and filter configuration Johannes Berg
2007-08-21 21:14 ` Ivo van Doorn
2007-08-22 9:23 ` Johannes Berg
2007-09-03 2:07 ` Daniel Drake
2007-09-03 8:36 ` Johannes Berg
2007-09-03 9:29 ` Johannes Berg
2007-09-03 10:57 ` Johannes Berg
2007-09-05 5:16 ` Ulrich Kunitz
2007-09-05 11:23 ` Johannes Berg
2007-09-05 14:16 ` Michael Buesch [this message]
2007-09-05 14:21 ` Johannes Berg
2007-09-05 14:23 ` Michael Wu
2007-09-05 14:33 ` Johannes Berg
2007-09-03 13:32 ` Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2007-08-15 15:25 [RFC 0/2] device configuration changes Johannes Berg
2007-08-15 15:25 ` [RFC 2/2] mac80211: revamp interface and filter configuration Johannes Berg
2007-08-16 12:41 ` 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=200709051616.25044.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=dsd@gentoo.org \
--cc=johannes@sipsolutions.net \
--cc=kune@deine-taler.de \
--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).