From: Stephen Hemminger <stephen.hemminger@vyatta.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-kernel@vgr.kernel.org
Subject: Re: qdisc and down links (regression)
Date: Fri, 8 Aug 2008 14:32:01 -0700 [thread overview]
Message-ID: <20080808143201.009caf54@extreme> (raw)
In-Reply-To: <20080807.185024.155026077.davem@davemloft.net>
On Thu, 07 Aug 2008 18:50:24 -0700 (PDT)
David Miller <davem@davemloft.net> wrote:
> From: David Miller <davem@davemloft.net>
> Date: Thu, 07 Aug 2008 15:47:35 -0700 (PDT)
>
> > From: Stephen Hemminger <stephen.hemminger@vyatta.com>
> > Date: Thu, 7 Aug 2008 14:30:36 -0700
> >
> > > Before the mulitqueue changes in 2.6.27-rc it was possible to setup
> > > queueing disciplines before the link came up (carrier active). This
> > > no longer works. If link is down, the qdisc is the noop_qdisc and
> > > any configuration changes don't seem to be shown.
> >
> > I'll see why this happens, it wasn't an intentional change.
>
> This should fix it, let me know if it doesn't:
It fixes it for qdisc but not for ingress filters
# tc qdisc add dev eth0 handle ffff: ingress
# tc filter add dev eth0 parent ffff: protocol ip \
prio 50 u32 match ip src 0.0.0.0/0 police rate 800kbit burst 10k drop flowid :1
RTNETLINK answers: Invalid argument
We have an error talking to the kernel
Another problem is that the ingress qdisc can no longer be deleted
successfully.
next prev parent reply other threads:[~2008-08-08 21:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 21:30 qdisc and down links (regression) Stephen Hemminger
2008-08-07 22:47 ` David Miller
2008-08-08 1:50 ` David Miller
2008-08-08 21:32 ` Stephen Hemminger [this message]
2008-08-08 23:11 ` David Miller
2008-08-08 23:12 ` Stephen Hemminger
2008-08-09 6:24 ` David Miller
2008-08-11 17:34 ` 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=20080808143201.009caf54@extreme \
--to=stephen.hemminger@vyatta.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vgr.kernel.org \
--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).