From: Jeff Garzik <jgarzik@pobox.com>
To: Tim Mattox <tmattox@gmail.com>
Cc: davem@redhat.com, hadi@cyberus.ca, netdev@oss.sgi.com
Subject: Re: [RFC,PATCH] fastroute dead code...
Date: Fri, 30 Jul 2004 17:08:54 -0400 [thread overview]
Message-ID: <410AB8E6.1010102@pobox.com> (raw)
In-Reply-To: <ea86ce2204073013292c055a3@mail.gmail.com>
Tim Mattox wrote:
>>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.
Driver use is completely irrelevant :)
Regardless of what any driver does, the IPv4 code in the kernel does not
make use of the RTCF_FAST flag, once set. All the fastrouting driver
support API/code amounts to precisely nothing.
Unless the --core net stack-- is patched again to support fastrouting,
all this is dead code.
Jeff
next prev parent reply other threads:[~2004-07-30 21:08 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
2004-07-30 21:08 ` Jeff Garzik [this message]
-- 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=410AB8E6.1010102@pobox.com \
--to=jgarzik@pobox.com \
--cc=davem@redhat.com \
--cc=hadi@cyberus.ca \
--cc=netdev@oss.sgi.com \
--cc=tmattox@gmail.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 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.