From: "Michael T. Babcock" <mbabcock@fibrespeed.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: TC Point & Click + XML
Date: Sun, 15 Jul 2001 01:40:59 +0000 [thread overview]
Message-ID: <marc-lartc-99516134702487@msgid-missing> (raw)
In-Reply-To: <marc-lartc-99499934900884@msgid-missing>
David Talbot wrote:
> This is logically the way I've always thought of tc/iptables etc (It
> makes sense to me that you would want to configure them both in the
> same file).
On a Linux machine -- yes. However, doing XML schemas correctly means
that it should describe one thing well, and only that one thing. I'd
rather have an extensible schema that describes traffic control rules
perfectly than one that also describes routing and filtering half-heartedly.
> Of course the example above means alot of things are implied such as
> the average packet size and many of the other parts of TC that are
> "unknown" (such as quantum, I still can't find and documentation as to
> what It does, I just know it has to be 1514b). In cases such as the
> one mentioned above, we could create "semi-intelligent defaults" but
> with the ability for the person to define it if they really want to.
Quantum is the unit of an individual packet and should be set to the MTU
+ the ethernet header size (14 bytes).
--
Michael T. Babcock
CTO, FibreSpeed
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
prev parent reply other threads:[~2001-07-15 1:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-13 4:41 [LARTC] Re: TC Point & Click + XML Michael T. Babcock
2001-07-13 13:27 ` David Talbot
2001-07-13 15:22 ` Michael T. Babcock
2001-07-13 15:53 ` Togan Muftuoglu
2001-07-13 18:49 ` David Talbot
2001-07-13 20:21 ` Michael T. Babcock
2001-07-13 22:04 ` David Talbot
2001-07-15 1:40 ` Michael T. Babcock [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-99516134702487@msgid-missing \
--to=mbabcock@fibrespeed.net \
--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.