From: Badalian Vyacheslav <slavon@bigtelecom.ru>
To: Patrick McHardy <kaber@trash.net>
Cc: Jarek Poplawski <jarkao2@gmail.com>, netdev@vger.kernel.org
Subject: Re: Packetlost when "tc qdisc del dev eth0 root"
Date: Wed, 16 Jan 2008 11:35:35 +0300 [thread overview]
Message-ID: <478DC1D7.90401@bigtelecom.ru> (raw)
In-Reply-To: <478DBADB.1080200@trash.net>
>
>
> Yes, thats one possibility (without the dummy device though please).
> But I wonder what this would actually be useful for. I don't think
> replacing the root qdisc by a different type is a common scenario,
> for the same type you can simply use "tc qdisc change", "tc class
> change" and "tc class replace".
>
> Badalian, what are you actually doing?
>
Sorry. Resend to all.
I simple recreate all rules. I change idea from do many
add,change,delete because have many kernel panics on many kernels 2.6.x
First i have panics on "delete filter" operation... was fix it...
great.. then have panics on "delete htb" operation... long time wait to
fix it (maintainer of tc not have time to fix it i think).. but have 1-5
panics at day.... i think my clients hate me =) i rewrite script to
simple recreate all rules... in this method i have small packetlost 1
time in hour (then recreate root qdisc), but not have panics... now i
use new logic of scripts... =)
maybe need go back to accurate logic of scripts, but i to fear kernel
panics =)
P.S. Feature request:
tc class show [ dev STRING ] [ root | parent CLASSID ]
may add classid filter to show?
i need do like this
/sbin/tc -s class show dev eth0 | grep -A2 "htb $HTB "
to get stats of class... but i every run real look all table.. its not good
Thanks that are you interesting history of my problems =)
Slavon.
next prev parent reply other threads:[~2008-01-16 8:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 11:10 Packetlost when "tc qdisc del dev eth0 root" Badalian Vyacheslav
2008-01-15 16:05 ` Patrick McHardy
2008-01-15 16:11 ` slavon
2008-01-15 21:15 ` Jarek Poplawski
2008-01-15 21:46 ` slavon
2008-01-15 22:04 ` slavon
2008-01-15 22:49 ` Jarek Poplawski
2008-01-16 5:12 ` Patrick McHardy
2008-01-19 23:21 ` Jarek Poplawski
2008-01-15 22:32 ` Jarek Poplawski
2008-01-15 23:16 ` Glen Turner
2008-01-16 5:02 ` Patrick McHardy
2008-01-16 8:02 ` Jarek Poplawski
2008-01-16 8:05 ` Patrick McHardy
2008-01-16 8:35 ` Badalian Vyacheslav [this message]
2008-01-16 9:42 ` Jarek Poplawski
2008-01-16 8:52 ` Jarek Poplawski
2008-01-16 8:54 ` Badalian Vyacheslav
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=478DC1D7.90401@bigtelecom.ru \
--to=slavon@bigtelecom.ru \
--cc=jarkao2@gmail.com \
--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).