Maybe I'm wrong, but MBS is MegaBytes/Sec and MbS is MegaBits/Sec.  KBS is
KiloBytes/Sec and KbS is KiloBits/Sec.

 

So you want 200KBS which is about 1600KbS, which is 1.6MbS.  If I've got the
math and numbers right here, then 200KBS this should not be a problem at
all.

 

Bill

 

From: [email protected]
[mailto:[email protected]] On Behalf
Of yueyue papa
Sent: Thursday, February 04, 2010 9:23 AM
To: Mailing list for lwIP users
Subject: Re: [lwip-users] lwIP performance

 

kbytes/s

 

Is there any suggest performance for lwIP?

 

eg: For ARM9 XX Mhz  yyy kbytes/s

 ...

 

I neeed to understand whether my 200k bytes/s is a reasonable speed in my
96M system. Otherwise I must find something to increase my network speed.

 

Lee



 

On Thu, Feb 4, 2010 at 6:44 PM, Kieran Mansley <[email protected]> wrote:

On Wed, 2010-02-03 at 23:27 +0800, yueyue papa wrote:
> Hi All,
>
> I make the 1.3.2 lwIP running in LAN environment.  My CPU is about 96M
> MIPS platform.
>
> FTP client is used as a download speed test, the current speed is
> about 200k/s.  Is it a reasonable speed for lwIP?
>
> I think the speed may be a bit slow, but I did not known the where is
> the problem.  I found the socket windows update will make the speed
> down heavily.
>
> My performance tune process
> 1> pull mode ==> interrupt mode
>      20k /s ==> 30k/s
> 2> removed some interrup delay and ...
>     30k/s ==> 80k/s
> 3> CPU freqent from 48M ==> 96M hz
>     80k/s ==> 180k/s
> 4> MSS 1K ==> 1460
>     180K/s ==> 196K/s

What units are your measurements in?  k/s could be Kilo-bits or
Kilo-bytes.  Your experiments suggest that your network speed is limited
by CPU speed, as everything you change to make it faster has reduced the
load on the CPU.


Kieran




_______________________________________________
lwip-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/lwip-users

 

_______________________________________________
lwip-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/lwip-users

Reply via email to