From: "Arend van Spriel" <arend@broadcom.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>
Subject: mac80211 flush callback
Date: Wed, 29 Aug 2012 13:32:52 +0200 [thread overview]
Message-ID: <503DFDE4.5030102@broadcom.com> (raw)
Hoi Johannes,
I ma currently looking into a long standing issue with flush callback in
brcmsmac. After some debugging I found out that mac80211 keeps pushing
packets to brcmsmac during the flush. Is that correct? Should brcmsmac
(or any other driver) stop the mac80211 queues during the flush? My
assumption was that mac80211 would not do transmits during the flush,
but it probably comes from another worker thread.
Gr. AvS
next reply other threads:[~2012-08-29 11:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 11:32 Arend van Spriel [this message]
2012-09-05 13:53 ` mac80211 flush callback Johannes Berg
2012-09-05 16:27 ` Arend van Spriel
2012-09-05 16:34 ` 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=503DFDE4.5030102@broadcom.com \
--to=arend@broadcom.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 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).