From: Patrick McHardy <kaber@trash.net>
To: Andi Kleen <ak@suse.de>
Cc: hadi@cyberus.ca, netdev@vger.kernel.org
Subject: Re: hard hang through qdisc
Date: Thu, 31 Jan 2008 14:29:50 +0100 [thread overview]
Message-ID: <47A1CD4E.7050701@trash.net> (raw)
In-Reply-To: <200801311428.48175.ak@suse.de>
Andi Kleen wrote:
>> ---------
>> lilsol:~# tc qdisc add dev eth0 root tbf rate 1000 burst 10 limit 100
>> lilsol:~# uname -a
>> Linux lilsol 2.6.24 #1 PREEMPT Sun Jan 27 09:22:00 EST 2008 i686
>
> Can you try it again with current git mainline?
I'll look into it.
next prev parent reply other threads:[~2008-01-31 13:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 12:21 hard hang through qdisc Andi Kleen
2008-01-31 12:34 ` jamal
2008-01-31 13:28 ` Andi Kleen
2008-01-31 13:29 ` Patrick McHardy [this message]
2008-01-31 14:02 ` Patrick McHardy
2008-01-31 15:04 ` Andi Kleen
2008-01-31 15:12 ` Patrick McHardy
2008-01-31 18:46 ` Patrick McHardy
2008-01-31 18:55 ` Andi Kleen
2008-01-31 12:43 ` hard hang through qdisc II Andi Kleen
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=47A1CD4E.7050701@trash.net \
--to=kaber@trash.net \
--cc=ak@suse.de \
--cc=hadi@cyberus.ca \
--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).