All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Rabbitson <rabbit@rabbit.us>
To: lartc@vger.kernel.org
Subject: [LARTC] Unclarified issue
Date: Mon, 12 May 2003 13:35:58 +0000	[thread overview]
Message-ID: <marc-lartc-105274679628578@msgid-missing> (raw)

Hi all,
Just finished reading and re-reading the advanced routing how-to. This this is marvelous!!! Thank you all that spent your 
time and devoted it to such a great paper! However there is something that I am missing from the picture. By default each 
interface is bundled with the pfifo_fast that prioritizes the packets based on TOS. If for say we do this:
# tc qdisc add dev eth0 root tbf rate 100kbit latency 100ms urst 2048
Do we actually lose the whole point of TOS? Or there is stil an underlying filter somewhere in the kernel that will take 
care of the TOS scheduling just like pfifo_fast did? 
Also in the following example:
# tc qdisc add dev eth0 root handle 1: prio
We automatically create three handles 1:1 1:2 1:3, with the default priomap. However what happens to traffic that goes down 
1:1 if there is no qdisc attached to it? Does it get dequeued right off the back or there is again something similar to 
pfifo_fast waiting for it? 

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

             reply	other threads:[~2003-05-12 13:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-12 13:35 Peter Rabbitson [this message]
2003-05-12 19:18 ` [LARTC] Unclarified issue Stef Coene
2003-05-12 21:08 ` Peter Rabbitson
2003-05-13 17:13 ` Stef Coene

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-105274679628578@msgid-missing \
    --to=rabbit@rabbit.us \
    --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.