All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Benc <jbenc@suse.cz>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: netdev@vger.kernel.org, Ivo Van Doorn <ivdoorn@gmail.com>,
	rt2400-devel@lists.sourceforge.net,
	Jouni Malinen <jkm@devicescape.com>,
	Simon Barber <simon@devicescape.com>
Subject: Re: d80211: How does TX flow control work?
Date: Wed, 10 Jan 2007 19:20:12 +0100	[thread overview]
Message-ID: <20070110192012.341b2612@griffin.suse.cz> (raw)
In-Reply-To: <45A2A728.1070404@web.de>

On Mon, 08 Jan 2007 21:18:48 +0100, Jan Kiszka wrote:
> The actual problem was meanwhile identified: shorewall happened to
> overwrite the queueing discipline of wmaster0 with pfifo_fast. I found
> the magic knob to tell shorewall to no longer do this (at least until I
> want to manage traffic control that way...), but I still wonder if it is
> an acceptable situation. Currently, the user can intentionally or
> accidentally screw up the stack this way.

Hm, we probably need a way to tell the kernel not to remove 802.11
qdisc. Jouni, Simon, is that possible or do we need to patch NET_SCHED
code?

Thanks,

 Jiri

-- 
Jiri Benc
SUSE Labs

  reply	other threads:[~2007-01-10 18:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-02 13:08 d80211: How does TX flow control work? Jan Kiszka
2007-01-03 17:52 ` Jiri Benc
2007-01-03 18:10   ` Jan Kiszka
2007-01-03 18:18     ` Jiri Benc
2007-01-03 18:50       ` Jan Kiszka
2007-01-07  0:00         ` Jan Kiszka
2007-01-08 20:18           ` Jan Kiszka
2007-01-10 18:20             ` Jiri Benc [this message]
2007-01-10 18:29               ` Simon Barber
2007-03-27 20:58             ` 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

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=20070110192012.341b2612@griffin.suse.cz \
    --to=jbenc@suse.cz \
    --cc=ivdoorn@gmail.com \
    --cc=jan.kiszka@web.de \
    --cc=jkm@devicescape.com \
    --cc=netdev@vger.kernel.org \
    --cc=rt2400-devel@lists.sourceforge.net \
    --cc=simon@devicescape.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.