All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jussi Mäki" <valen@ihanaa.org>
To: lartc@vger.kernel.org
Subject: [LARTC] really weird problem with 2.2.20 kernel
Date: Tue, 13 Aug 2002 19:58:33 +0000	[thread overview]
Message-ID: <marc-lartc-102926877423805@msgid-missing> (raw)


I'm trying to limit the available bandwidth for an single ip address, i've
got 3 different scripts which all work with kernel 2.2.17 and all the
2.4.x kernel's i've tested..

The problem is that when for example i limit the traffic to 512kbit/s i'm
only getting about 300kbit/s and this is only with 2.2.20 kernel..

I've tried htb and cbq with different schudulers like sfq and pfifo and
all of them have the exact same problem.

I'm not very keen on upgrading to kernel 2.4.x as i have to upgrade quite
a few machine's at once and none of them have compilation tools.

Any ideas?

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2002-08-13 19:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-13 19:58 Jussi Mäki [this message]
2002-08-13 20:12 ` [LARTC] really weird problem with 2.2.20 kernel Stef Coene
2002-08-14  5:32 ` Jussi Mäki

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=marc-lartc-102926877423805@msgid-missing \
    --to=valen@ihanaa.org \
    --cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.