From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Confusion about kernelconfig QoS-options
Date: Thu, 29 Aug 2002 16:50:32 +0000 [thread overview]
Message-ID: <marc-lartc-103063990416277@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103063533710026@msgid-missing>
On Thursday 29 August 2002 18:25, Nils Lichtenfeld wrote:
> Hi Stef!
>
> Stef Coene schrieb:
> >> Witch of the following options _NEED_ to be enabled? I ask, because
> >> the goal is to have the kernel as small as possible.
> >
> > Then use modules and load only the modules you need.
>
> That was not my question. The listed items are not selectable as
> modules. They can only be compiled into the kernel or turned off. I list
> them again, they reside in the < QOS and/or fair queueing > section:
>
> [*] QoS support
Only needed if you want to implement QOS support so other devices on the
network can send requestst for bandwidth.
> [*] Rate estimator
This can be used for the "Traffic policing" to calculate the rate of the
packets.
> [*] Traffic policing
This is sort of tbf-in-filter. You can configure a filter to only match
packets at a certain rate.
You don't need these options to use SFQ, HTB, fw and/or u32.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-08-29 16:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-29 15:40 [LARTC] Confusion about kernelconfig QoS-options Nils Lichtenfeld
2002-08-29 16:04 ` Stef Coene
2002-08-29 16:25 ` Nils Lichtenfeld
2002-08-29 16:50 ` Stef Coene [this message]
2002-08-29 17:12 ` Nils Lichtenfeld
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-103063990416277@msgid-missing \
--to=stef.coene@docum.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.