From: Jan Kiszka <jan.kiszka@web.de>
To: Michael Wu <flamingice@sourmilk.net>
Cc: Jiri Benc <jbenc@suse.cz>,
Johannes Berg <johannes@sipsolutions.net>,
Ivo Van Doorn <ivdoorn@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: d80211: How does TX flow control work?
Date: Tue, 01 May 2007 20:57:07 +0200 [thread overview]
Message-ID: <46378D83.7020706@web.de> (raw)
In-Reply-To: <200705011301.24478.flamingice@sourmilk.net>
[-- Attachment #1: Type: text/plain, Size: 933 bytes --]
Michael Wu wrote:
> On Tuesday 01 May 2007 11:25, Jiri Benc wrote:
>> On Tue, 01 May 2007 16:18:52 +0200, Jan Kiszka wrote:
>>> Already tried this lethal command? Works "fine" here...
>>>
>>> #tc qdisc del dev wmaster0 root
>> I cannot reproduce it too.
>>
> I can reproduce it.
Fine, that save /me some time.
> I thought qdiscs couldn't be changed without taking the
> interface down first.. which is not true. It merely waits for things to quiet
> down before swapping out the qdisc.
>
> Some code in ieee80211_master_start_xmit probably will be needed to correctly
> handle things if the ieee80211 qdisc isn't installed. I don't see an easy way
> to prevent things from working all the time if the qdisc is removed.
I didn't followed the discussion in details, but wasn't there once a
suggestion to hide netdevices from the user so that there would be no
chance to stumble over this issue?
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]
prev parent reply other threads:[~2007-05-01 18:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <459A5945.80909@web.de>
[not found] ` <20070103185203.2754e059@griffin.suse.cz>
[not found] ` <459BF179.6000906@web.de>
[not found] ` <20070103191853.4f440b8b@griffin.suse.cz>
[not found] ` <459BFB05.9040608@web.de>
[not found] ` <45A03825.9080807@web.de>
[not found] ` <45A2A728.1070404@web.de>
2007-03-27 20:58 ` d80211: How does TX flow control work? Johannes Berg
2007-03-29 8:45 ` Jan Kiszka
2007-05-01 10:41 ` Jan Kiszka
2007-05-01 10:47 ` Jiri Benc
2007-05-01 10:50 ` Jan Kiszka
2007-05-01 11:04 ` Johannes Berg
2007-05-01 13:07 ` Jan Kiszka
2007-05-01 13:26 ` Johannes Berg
2007-05-01 14:18 ` Jan Kiszka
2007-05-01 15:25 ` Jiri Benc
2007-05-01 17:01 ` Michael Wu
2007-05-01 18:57 ` Jan Kiszka [this message]
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=46378D83.7020706@web.de \
--to=jan.kiszka@web.de \
--cc=flamingice@sourmilk.net \
--cc=ivdoorn@gmail.com \
--cc=jbenc@suse.cz \
--cc=johannes@sipsolutions.net \
--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).