From: Adi Nugroho <Adi@iNterNUX.co.id>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Latency in SFQ --> Done
Date: Thu, 20 Dec 2001 05:27:53 +0000 [thread overview]
Message-ID: <marc-lartc-100882575506429@msgid-missing> (raw)
On Tuesday 18 December 2001 16:03, bert hubert wrote:
> > If we are using TBF, we can reduce "buffer" and "limit" to minimize
> > latency. What should we do in SFQ?
>
> You can't really. SFQ has a fixed queue length of 128.
>
Dear Sirs,
It worked now.
Thank you for all help, from this mailing list and from IRC.
Special Thanks for Mr. Hubert
I have reduce the buffer (queue length) from 128 to 15, and it works very
nice, very well, and very fair.
What I did was:
1. Open the sfq source (/usr/src/linux/net/sched/sch_sfq.c)
2. In about line 91, there is "#define SFQ_DEPTH 128"
3. Change it to "#define SFQ_DEPTH 15"
4. Recompile kernel (modules)
5. Restart (I'm not sure it is needed. modprobe should be enough)
6. Run it again
7. Nice...nice....nice.....
For Mr. Kuznetsov, if you don't mind, I would like to suggest to give a
chance to the user to change it manually in run time, like we can change
quantum and perturb. (in the next release, of course)
In developed countries, queue depth 128 is fair, since we are talking about
high speed network.
In my case, I just use 64 kbit bandwidth for every 4 Internet caffee, which
used by about 15 computers each. Very slow speed.... need very small queue
length.
Regards,
Adi Nugroho
Who are very happy now :-)
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next reply other threads:[~2001-12-20 5:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-20 5:27 Adi Nugroho [this message]
2002-01-09 3:30 ` [LARTC] Latency in SFQ --> Done Alexey Kuznetsov
2002-01-10 5:36 ` Adi Nugroho
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-100882575506429@msgid-missing \
--to=adi@internux.co.id \
--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.