netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: hadi@cyberus.ca
Cc: "David S. Miller" <davem@redhat.com>,
	tmattox@gmail.com, netdev@oss.sgi.com,
	Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [RFC,PATCH] fastroute dead code...
Date: Fri, 30 Jul 2004 17:11:03 -0400	[thread overview]
Message-ID: <410AB967.2010202@pobox.com> (raw)
In-Reply-To: <1091219266.1029.470.camel@jzny.localdomain>

jamal wrote:
> On Fri, 2004-07-30 at 16:10, David S. Miller wrote:
>>I totally agree.  And people can always resurrect it from the
>>repository history or an old tarball if they wish.
> 
> 
> Patches are needed for the driver to use that code. So its not entirely
> dead code i.e it is referenced from fastroute enabled drivers.
> Sample (really old) code found at:
> http://ftp.iasi.roedu.net/mirrors/ftp.inr.ac.ru/ip-routing/fastroute/


Actually the opposite...  the driver infrastructure is pretty much in 
place.  It's the core IPv4 routing code that no longer does what people 
think :)

grep for RTCF_FAST in 2.4.x and then in 2.6.x...

	Jeff

  reply	other threads:[~2004-07-30 21:11 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 [this message]
2004-08-02 11:45       ` Andi Kleen
2004-07-30 20:29     ` Tim Mattox
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=410AB967.2010202@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=davem@redhat.com \
    --cc=hadi@cyberus.ca \
    --cc=netdev@oss.sgi.com \
    --cc=ralf@linux-mips.org \
    --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 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).