From: kuznet@ms2.inr.ac.ru
To: linux-kernel@vger.kernel.org
Cc: creatix@hipac.org
Subject: Re: tc stack overflow
Date: Tue, 8 Jul 2003 20:47:19 +0400 (MSD) [thread overview]
Message-ID: <200307081647.UAA13391@dub.inr.ac.ru> (raw)
In-Reply-To: <200307081640.UAA28623@th.inr.ac.ru> from "A.N.Kuznetsov" at =?ISO-8859-1?Q?=20=E9?= =?ISO-8859-1?Q?=C0=CC?= 08, 2003 08:40:05
Hello!
> # tc qdisc add dev eth0 root handle 1: prio \
> for i in `seq 500` ; do tc qdisc add dev eth0 \
> parent $i:1 handle `expr $i + 1`: prio ; done ; \
> ping 1.2.3.4
>
> [replace eth0 by a device of your choice]
... or replace too complicated script with cp /dev/zero /dev/mem. :-)
> So, what do you think about the issue? Do you care?
I do not. Yes, it is real design mistake, recursion is always evil.
Maybe, it will be remade some day. But until that day it does not matter.
Alexey
next parent reply other threads:[~2003-07-08 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200307081640.UAA28623@th.inr.ac.ru>
2003-07-08 16:47 ` kuznet [this message]
2003-07-05 22:21 tc stack overflow Thomas Heinz
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=200307081647.UAA13391@dub.inr.ac.ru \
--to=kuznet@ms2.inr.ac.ru \
--cc=creatix@hipac.org \
--cc=linux-kernel@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).