From: Jarek Poplawski <jarkao2@gmail.com>
To: Patrick McHardy <kaber@trash.net>
Cc: Badalian Vyacheslav <slavon@bigtelecom.ru>, netdev@vger.kernel.org
Subject: Re: Packetlost when "tc qdisc del dev eth0 root"
Date: Wed, 16 Jan 2008 09:52:55 +0100 [thread overview]
Message-ID: <20080116085254.GB2307@ff.dom.local> (raw)
In-Reply-To: <478DBADB.1080200@trash.net>
On Wed, Jan 16, 2008 at 09:05:47AM +0100, Patrick McHardy wrote:
...
> 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?
I'm not sure Vyacheslav needs just this, but I've thought about the
possibility to recreate the 'shadow' copy of currently used qdisc
tree (with some updates of course) while it's running. So, the
possibility of using all the same handles and classids, and even
dev names if possible, and doing such a switch without any visible
break.
Jarek P.
next prev parent reply other threads:[~2008-01-16 8:46 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
2008-01-16 9:42 ` Jarek Poplawski
2008-01-16 8:52 ` Jarek Poplawski [this message]
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=20080116085254.GB2307@ff.dom.local \
--to=jarkao2@gmail.com \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=slavon@bigtelecom.ru \
/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).