All of lore.kernel.org
 help / color / mirror / Atom feed
From: Malte Starostik <malte.starostik@t-online.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Problems using The Ultimate Traffic Conditioner from the Cookbook
Date: Sun, 28 Dec 2003 08:31:24 +0000	[thread overview]
Message-ID: <marc-lartc-107260309132410@msgid-missing> (raw)
In-Reply-To: <marc-lartc-107181174021910@msgid-missing>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

On Thursday 25 December 2003 09:43, Kabelweb wrote:
> Hi!
>
> > So I played a bit with the DOWNLINK value and found out that down to and
> > including 555 no packets are dropped even if a download fully saturates
> > the link while 554 already drastically caps the download to ~65 kbytes/s,
> > and there are packets being dropped:
>
> It seems that your setup suffers from timer inaccuracy.
> This topic has been dealt with some times on this list.
>
> Read (for example) this thread:
> 	http://www.mail-archive.com/lartc@mailman.ds9a.nl/msg02795.html
>
[snip]

> The solution (as mentioned in the thread above) is to either change the HZ
> value to for example 1024 (you don't have to do this by manually patching
> your kernel source because your gentoo kernel has a patch applied which
> lets you specify the HZ value from kernel config - I think its somewhere in
> "Processor type and features") or to change PSCHED_CLOCK_SOURCE to
> PSCHED_CPU in your /usr/src/linux/include/net/pkt_sched.h (which I
> personally had some problems with in the past - can't remember exactly
> though).
>
> I hope this helps - let us know...

Thanks Andreas, this helped perfectly. I used the latter approach by editing
pkt_sched.h to use the rtdsc as I was a little intimidated by the help text
for the HZ option mentioning not to use values larger than half the CPU's
clock in MHz. And as this is only a PII/266 I thought gentoo's default of 200
was stressing that enough already...

Regards,
- -Malte
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/7pTfVDF3RdLzx4cRAoObAJ9Ek0pVzNy5hh/r85W+qbeNaTecOQCg0qCw
CtBhWYt6k32swyujNpRtNBo=fmYt
-----END PGP SIGNATURE-----
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2003-12-28  8:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-19  5:06 [LARTC] Problems using The Ultimate Traffic Conditioner from the Cookbook Malte Starostik
2003-12-25  8:43 ` Kabelweb
2003-12-28  8:31 ` Malte Starostik [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=marc-lartc-107260309132410@msgid-missing \
    --to=malte.starostik@t-online.de \
    --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.