From: Stephen Hemminger <stephen.hemminger@vyatta.com>
To: David Miller <davem@davemloft.net>
Cc: kaber@trash.net, netdev@vger.kernel.org
Subject: Re: sfq dump broken in 2.6.27-rc1
Date: Wed, 6 Aug 2008 20:20:29 -0700 [thread overview]
Message-ID: <20080806202029.63f25c81@extreme> (raw)
In-Reply-To: <20080806.181327.139395860.davem@davemloft.net>
On Wed, 06 Aug 2008 18:13:27 -0700 (PDT)
David Miller <davem@davemloft.net> wrote:
> From: Stephen Hemminger <stephen.hemminger@vyatta.com>
> Date: Wed, 6 Aug 2008 18:02:37 -0700
>
> > With only one sfq (on eth0), I am getting multiple results from
> > 'tc qdisc ls'
> >
> > # tc qdisc ls
> > qdisc sfq 8001: dev eth0 root limit 127p quantum 1514b
> > qdisc sfq 8001: dev eth0 root limit 127p quantum 1514b
> > qdisc sfq 8001: dev eth0 root limit 127p quantum 1514b
> > qdisc sfq 8001: dev eth0 root limit 127p quantum 1514b
> > qdisc sfq 8001: dev eth0 root limit 127p quantum 1514b
> >
> > Still bisecting, since there is no obvious reason for the sudden borkage.
>
> Don't bother bisecting, it will take longer than the obvious
> set of debug printk's you could add to net/sched/sch_api.c:tc_dump_qdisc().
>
> Please use a "mindful" approach to debugging this instead of
> a "mindless" one like bisect :-)
What ever happened to "you broke it, you fix it?"
next prev parent reply other threads:[~2008-08-07 3:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 1:02 sfq dump broken in 2.6.27-rc1 Stephen Hemminger
2008-08-07 1:13 ` David Miller
2008-08-07 3:20 ` Stephen Hemminger [this message]
2008-08-07 3:22 ` David Miller
2008-08-07 6:08 ` [PATCH] net: trap attempts to modify noop qdisc Stephen Hemminger
2008-08-07 6:11 ` David Miller
2008-08-07 6:15 ` Stephen Hemminger
2008-08-07 6:18 ` David Miller
[not found] ` <20080806.233703.193701199.davem@davemloft.net>
2008-08-07 17:22 ` Stephen Hemminger
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=20080806202029.63f25c81@extreme \
--to=stephen.hemminger@vyatta.com \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=netdev@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).