Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Michael T. Babcock" <mbabcock@fibrespeed.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] problem with the howto sample
Date: Fri, 07 Dec 2001 04:35:11 +0000	[thread overview]
Message-ID: <marc-lartc-100769979321575@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100767692924897@msgid-missing>

On Thu, Dec 06, 2001 at 11:14:01PM +0100, Patrick Nagelschmidt wrote:
> is the naming of classes essential for building them correctly? is 
> parent 1:1 classid 10:0 somehow different from parent 1:1 classid 1:2? 
> up to now i thought classid was only a name and the parent would be 
> enough to make the classes' positions in the tree unambiguously...

If we were to rework the naming, something like ...

1) parent 1: classid 1:2
2) parent 1:2 classid 1:2:5
3) parent 1:2:5 classid 1:2:5:8

... would make more sense.

The numbering scheme currently in place makes very little sense and is 
quite wasteful of the number-space it uses (not that it matters much to 
most people).

If the above were used, 'parent' would become quite unnecessary of course.
-- 
Michael T. Babcock
CTO, FibreSpeed Ltd.     (Hosting, Security, Consultation, Database, etc)
http://www.fibrespeed.net/~mbabcock/

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/

      parent reply	other threads:[~2001-12-07  4:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-06 22:14 [LARTC] problem with the howto sample Patrick Nagelschmidt
2001-12-06 22:52 ` bert hubert
2001-12-06 23:14 ` Patrick Nagelschmidt
2001-12-06 23:19 ` bert hubert
2001-12-07  0:17 ` Patrick Nagelschmidt
2001-12-07  4:35 ` 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-100769979321575@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox