| To: | hadi@xxxxxxxxxx |
|---|---|
| Subject: | Re: [RFC,PATCH] fastroute dead code... |
| From: | Jeff Garzik <jgarzik@xxxxxxxxx> |
| Date: | Fri, 30 Jul 2004 17:11:03 -0400 |
| Cc: | "David S. Miller" <davem@xxxxxxxxxx>, tmattox@xxxxxxxxx, netdev@xxxxxxxxxxx, Ralf Baechle <ralf@xxxxxxxxxxxxxx> |
| In-reply-to: | <1091219266.1029.470.camel@xxxxxxxxxxxxxxxx> |
| References: | <20040730060348.GA22854@xxxxxxxxxxxxx> <ea86ce220407301229522be64f@xxxxxxxxxxxxxx> <20040730193515.GA11365@xxxxxxxxxxxxx> <20040730131004.2be1274d.davem@xxxxxxxxxx> <1091219266.1029.470.camel@xxxxxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510 |
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
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [RFC,PATCH] fastroute dead code..., Jeff Garzik |
|---|---|
| Next by Date: | Re: gigabit trouble, Francois Romieu |
| Previous by Thread: | Re: [RFC,PATCH] fastroute dead code..., jamal |
| Next by Thread: | Re: [RFC,PATCH] fastroute dead code..., Tim Mattox |
| Indexes: | [Date] [Thread] [Top] [All Lists] |