This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: ethernet performance <TCPIP guru question>
- From: Andrew Lunn <andrew dot lunn at ascom dot ch>
- To: Stephen Whitaker <whitaker at binarywave dot ca>
- Cc: "'eocs'" <ecos-discuss at sources dot redhat dot com>, Gary Thomas <gthomas at redhat dot com>, David Webster <dwebster at lanergy dot com>, "'Stephen Polkowski'" <stephen at centtech dot com>
- Date: Fri, 26 Apr 2002 16:36:05 +0200
- Subject: Re: [ECOS] ethernet performance <TCPIP guru question>
- References: <001001c1ed15$b5324030$4103a8c0@LANERGY05> <1019825680.15687.278.camel@hermes> <3CC96391.D376A12E@binarywave.ca>
On Fri, Apr 26, 2002 at 10:26:25AM -0400, Stephen Whitaker wrote:
> Hi Guys,
>
> I've also been looking at some minor performance improvements with
> the current eCos TCP/IP stack. A very simple change, would be to
> revert the call to ip_randomid() from ip_output(), when it fills
> in the IP header, back to just incrementing the ID. From what
> I've heard this improvement was made to help increase the
> security level of the stack, however, the overhead relative
> to the original method is significant.
I could be reading the code wrong, but it looks to me that
ip_randomid() is only called when doing IP forwording, ie a router, or
when using IP raw sockets.
Unless you happen to be doing either of these, i don't think it will
make a difference to you.
Please correct me if im wrong.
Andrew
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss