From: Tim Mattox <tmattox@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: davem@redhat.com, hadi@cyberus.ca, netdev@oss.sgi.com
Subject: Re: [RFC,PATCH] fastroute dead code...
Date: Fri, 30 Jul 2004 16:29:05 -0400 [thread overview]
Message-ID: <ea86ce2204073013292c055a3@mail.gmail.com> (raw)
In-Reply-To: <20040730193515.GA11365@havoc.gtf.org>
The code that uses (used?) fastroute is not in mainline. AFAIK there were
two ethernet drivers that you could load that used it, one tulip based
and the other 8390 based. Here's one of several archives of the
ancient driver code:
http://www.linuxgrill.com/anonymous/fire/alexey/fastroute/
They do not look like they have been maintained, in many years. It dates
from early 2.2 kernel days. Apparently in it's day, a Linux box with fastroute
could keep up with a Cisco router, but I've not been able to find the relevant
benchmark numbers via google as of yet, and I've stopped looking.
So, yes, I don't dispute that it's dead code as seen in mainline kernel source,
and should probably be removed now. If it was still important, we would
have seen fastroute GigE drivers by now, IMHO.
On Fri, 30 Jul 2004 15:35:15 -0400, Jeff Garzik <jgarzik@pobox.com> wrote:
[snip]
> Well my main point is that the code _doesn't do anything_.
>
> It is dead code, as-is, in the kernel. It would require patches to
> actually work at all.
>
> It is impossible that fastrouting is being actively used, without patches.
>
> Jeff
Some might consider dropping in a new network driver module a patch,
others wouldn't... Anyway, as I said before, IMHO I agree its dead code
worthy of removal unless someone comes up with a GigE driver that
actually uses it.
--
Tim Mattox - tmattox@gmail.com - http://homepage.mac.com/tmattox/
next prev parent reply other threads:[~2004-07-30 20:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-30 6:03 [RFC,PATCH] fastroute dead code Jeff Garzik
2004-07-30 19:29 ` Tim Mattox
2004-07-30 19:35 ` Jeff Garzik
2004-07-30 20:10 ` David S. Miller
2004-07-30 20:27 ` jamal
2004-07-30 21:11 ` Jeff Garzik
2004-08-02 11:45 ` Andi Kleen
2004-07-30 20:29 ` Tim Mattox [this message]
2004-07-30 21:08 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2004-07-30 20:31 Manish Lachwani
2004-07-30 21:05 ` jamal
2004-08-02 15:26 ` Kumar Gala
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=ea86ce2204073013292c055a3@mail.gmail.com \
--to=tmattox@gmail.com \
--cc=davem@redhat.com \
--cc=hadi@cyberus.ca \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.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).