From: "David S. Miller" <davem@davemloft.net>
To: Steven Blake <slblake@petri-meat.com>
Cc: Robert.Olsson@data.slu.se, netdev@oss.sgi.com
Subject: Re: Move fib_alias out of fib_hash.c
Date: Wed, 29 Sep 2004 14:27:50 -0700 [thread overview]
Message-ID: <20040929142750.27b35952.davem@davemloft.net> (raw)
In-Reply-To: <1096492842.2344.57.camel@localhost.localdomain>
On Wed, 29 Sep 2004 17:20:43 -0400
Steven Blake <slblake@petri-meat.com> wrote:
> > It can also
> > be the case that the longest matching prefix entry has no matching
> > TOS key, whereas a shorter prefix does.
>
> No routing protocols are distributing TOS-specific routes, and there is
> no prospect of that feature ever coming back. Why pay the cost of
> matching TOS on every packet forwarded?
Because once we add functionality to the kernel we can't simply
rip it out. People do use TOS routing, via static routes or
similar.
next prev parent reply other threads:[~2004-09-29 21:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-29 4:47 Move fib_alias out of fib_hash.c David S. Miller
2004-09-29 15:20 ` Robert Olsson
2004-09-29 19:53 ` David S. Miller
2004-09-29 21:20 ` Steven Blake
2004-09-29 21:27 ` David S. Miller [this message]
2004-09-29 22:09 ` Andi Kleen
2004-09-29 22:24 ` Ben Greear
2004-09-30 8:08 ` Andi Kleen
2004-09-30 15:51 ` Ben Greear
2004-09-29 21:43 ` Robert Olsson
2004-09-29 21:30 ` Robert Olsson
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=20040929142750.27b35952.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Robert.Olsson@data.slu.se \
--cc=netdev@oss.sgi.com \
--cc=slblake@petri-meat.com \
/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;
as well as URLs for NNTP newsgroup(s).