netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Badalian Vyacheslav <slavon@bigtelecom.ru>
To: Jarek Poplawski <jarkao2@gmail.com>
Cc: Patrick McHardy <kaber@trash.net>, netdev@vger.kernel.org
Subject: Re: Packetlost when "tc qdisc del dev eth0 root"
Date: Wed, 16 Jan 2008 11:54:59 +0300	[thread overview]
Message-ID: <478DC663.4000502@bigtelecom.ru> (raw)
In-Reply-To: <20080116085254.GB2307@ff.dom.local>

Jarek Poplawski пишет:
> 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.
>
>   
I also think that system must forward all packets what it get if it not 
dropped manual (by iptables or shaper).
Maybe someone need to test delete big TREE.. simple delete, not 
recreate... linux unavailable some time (if its realy big table its time 
may be 10-20 sec on 2xXeon).
I think need helper to do that operations more accurate. Now see 
situation that linux is PPTP server... its get 2000k connection... try 
delete qdisc on eth0 (incoming from wan to pptp clients)... i think many 
sessions will drop.

Thanks!

      reply	other threads:[~2008-01-16  8:55 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
2008-01-16  8:54             ` Badalian Vyacheslav [this message]

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=478DC663.4000502@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).