From: Szymon Miotk <spam@crocom.com.pl>
To: Patrick McHardy <kaber@trash.net>
Cc: Thomas Graf <tgraf@suug.ch>, netdev@oss.sgi.com, davem@davemloft.net
Subject: Re: PROBLEM: IProute hangs after running traffic shaping scripts
Date: Wed, 10 Nov 2004 13:08:14 +0100 [thread overview]
Message-ID: <419204AE.7030805@crocom.com.pl> (raw)
In-Reply-To: <418FCD0A.4040202@trash.net>
Patrick McHardy wrote:
> Thomas Graf wrote:
>
>> * Patrick McHardy <418F9AD0.1040701@trash.net> 2004-11-08 17:12
>>
>>
>>> There is some optimization possible, I will do this for the final
>>> patch. But I don't understand the problem you refer to, can you
>>> please explain ?
>>>
>>
>> I don't have the time to verify this at the moment but:
>>
>> 1) qdisc_destroy unlinking all the lists
>> 2) RTM_NEWQDISC creating a new qdisc with the same major classid as
>> the old one
>> which will suceed since the old one cannot be found anymore.
>> 3) rcu callback __qdisc_destroy -> qdisc_destroy looking through
>> qdisc_list
>> again and then deleting the new entries because their major classid
>> matches.
>>
>> I might be missing something though.
>>
> You're right, thanks. The optimization already fixed this, but I
> wasn't aware of the bug :) New patch attached.
I've tested the new kernel (2.6.10-rc1_bk17) with this patch.
It performed well on test system (reloading my traffic shaping
configuration for 100 times).
Now it forks for some 22 hours on production system, under normal load
(~20 Mbit, 500 clients at a time, 15000 entires in route table) and it
performs well.
Thanks a lot for your help, it really saved me away from troubles.
Szymon Miotk
prev parent reply other threads:[~2004-11-10 12:08 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-05 9:48 PROBLEM: IProute hangs after running traffic shaping scripts Szymon Miotk
2004-11-05 11:54 ` Thomas Graf
2004-11-05 14:16 ` [PATCH] PKT_SCHED: Initialize list field in dummy qdiscs Thomas Graf
2004-11-05 16:12 ` Patrick McHardy
2004-11-05 16:39 ` Thomas Graf
2004-11-05 17:26 ` Patrick McHardy
2004-11-05 17:58 ` Thomas Graf
2004-11-05 18:18 ` Patrick McHardy
2004-11-05 19:43 ` Thomas Graf
2004-11-06 1:18 ` Thomas Graf
2004-11-06 1:47 ` Patrick McHardy
2004-11-06 1:59 ` Thomas Graf
2004-11-06 14:50 ` Thomas Graf
2004-11-07 8:57 ` Patrick McHardy
2004-11-07 14:00 ` Thomas Graf
2004-11-07 16:19 ` Patrick McHardy
2004-11-07 16:33 ` Thomas Graf
2004-11-07 17:02 ` Patrick McHardy
2004-11-07 17:49 ` Thomas Graf
2004-11-07 18:22 ` Patrick McHardy
2004-11-07 19:08 ` Thomas Graf
2004-11-06 0:36 ` David S. Miller
2004-11-07 22:22 ` PROBLEM: IProute hangs after running traffic shaping scripts Patrick McHardy
2004-11-08 1:40 ` Patrick McHardy
2004-11-08 13:54 ` Thomas Graf
2004-11-08 16:12 ` Patrick McHardy
2004-11-08 18:33 ` Thomas Graf
2004-11-08 19:46 ` Patrick McHardy
2004-11-08 20:15 ` Thomas Graf
2004-11-10 0:18 ` David S. Miller
2004-11-10 0:40 ` Patrick McHardy
2004-11-10 0:55 ` Patrick McHardy
2004-11-10 6:13 ` David S. Miller
2004-11-10 12:08 ` Szymon Miotk [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=419204AE.7030805@crocom.com.pl \
--to=spam@crocom.com.pl \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=netdev@oss.sgi.com \
--cc=tgraf@suug.ch \
/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).