From: Kumar Gala <kumar.gala@freescale.com>
To: Manish Lachwani <Manish_Lachwani@pmc-sierra.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, <netdev@oss.sgi.com>,
<tmattox@gmail.com>, <hadi@cyberus.ca>,
Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [RFC,PATCH] fastroute dead code...
Date: Mon, 2 Aug 2004 10:26:36 -0500 [thread overview]
Message-ID: <578EC36E-E498-11D8-939F-000393DBC2E8@freescale.com> (raw)
In-Reply-To: <9DFF23E1E33391449FDC324526D1F25902833769@sjc1exm02.pmc_nt.nt.pmc-sierra.bc.ca>
I want to say an internal group in Freescale has seen similar style
performance improvements for integrated gig-e controllers in 2.4.
- kumar
On Jul 30, 2004, at 3:31 PM, Manish Lachwani wrote:
> Is this a 2.6 issue or a 2.4 issue? This is because I am using 2.4.21
> kernel and so do the customers of the board. This board supports 1.0
> Ghz PMC-Sierra Rm9000 processor. With fast routing, the IP forwarding
> numbers are about 900 Kpps. While in the case where there is no fast
> routing, the numbers are about 450 Kpps (NAPI enabled)
>
> I still have not done any 2.6 benchmarking since the board support is
> not completely functional in 2.6 as yet.
>
> Thanks
> Manish
>
> -----Original Message-----
> From: jamal [mailto:hadi@cyberus.ca]
> Sent: Friday, July 30, 2004 1:35 PM
> To: Manish Lachwani
> Cc: Jeff Garzik; tmattox@gmail.com; netdev@oss.sgi.com; Ralf Baechle
> Subject: Re: [RFC,PATCH] fastroute dead code...
>
>
> On Fri, 2004-07-30 at 16:10, David S. Miller wrote:
>> On Fri, 30 Jul 2004 15:35:15 -0400
>> Jeff Garzik <jgarzik@pobox.com> 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.
>>
>> 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/
>
>
>> I think it should be killed entirely, and that's what I'm going
>> to do.
>
> Nod from here.
> Before you kill it lets hear from Ralf who is acquinted with someone
> that uses it and sings praises of it (although i personaly dont believe
> it ;->).
>
> cheers,
> jamal
next prev parent reply other threads:[~2004-08-02 15:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-30 20:31 [RFC,PATCH] fastroute dead code Manish Lachwani
2004-07-30 21:05 ` jamal
2004-08-02 15:26 ` Kumar Gala [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-30 6:03 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
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=578EC36E-E498-11D8-939F-000393DBC2E8@freescale.com \
--to=kumar.gala@freescale.com \
--cc=Manish_Lachwani@pmc-sierra.com \
--cc=hadi@cyberus.ca \
--cc=jgarzik@pobox.com \
--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 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.