From: "Theepan" <tornado@linuxfromscratch.org>
To: lartc@vger.kernel.org
Subject: [LARTC] pfifo_fast with bands
Date: Fri, 30 Mar 2001 00:59:45 +0000 [thread overview]
Message-ID: <marc-lartc-98591406013252@msgid-missing> (raw)
Hello,
I read about the pfifo_fast has 3 bands, which allow you to prioritize
traffic into these bands. I cannot find anything about these bands in the tc
command reference (http://linux.bergqvist.se/tc/). I might be looking the
wrong place - in which case, where should I look for help with this qdisc?
The idea is to give "time-critical" sessions such as ssh, telnet etc.
HIGHEST priority (based on fwmark), so these will not lag no matter how much
the connection is overloaded.
I was thinking somewhere in line of:
- letting the firewall mark the packets as they come in and go out (if the
ports match of course).
- use tc to throw them into bands in the pfifi_fast queue, where these
marked packets will be thrown into band 1, and the rest in into band 3 -
here by servicing the "time-critical" services before fx downloads.
Can this be done without it getting too complex with CBQ and stuff?
- Theepan
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
reply other threads:[~2001-03-30 0:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-98591406013252@msgid-missing \
--to=tornado@linuxfromscratch.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox