[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lwip-devel] Re: [task #7040] Work on tcp_enqueue
From: |
Jonathan Larmour |
Subject: |
Re: [lwip-devel] Re: [task #7040] Work on tcp_enqueue |
Date: |
Wed, 04 Feb 2009 09:57:48 +0000 |
User-agent: |
Thunderbird 1.5.0.12 (X11/20070530) |
bill wrote:
>
> I agree. I suppose we don't know the breakdown of the use of lwIP. Are
> there 3 categories:
>
> 1) Smallest code size possible. Bandwidth doesn't matter.
> 2) Highest bandwidth possible. Code size don't matter.
> 3) No requirement for either code or bandwidth.
>
> I've left RAM requirements out because it is already highly configurable.
I think it's all in the project name :-).
But to some extent it's true that code size is a lot cheaper than RAM size
and there's more freedom, so it ends up as a balance.
Jifl
--
eCosCentric Limited http://www.eCosCentric.com/ The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["Si fractum non sit, noli id reficere"]------ Opinions==mine
- [lwip-devel] Re: [task #7040] Work on tcp_enqueue, (continued)
RE: [lwip-devel] Re: [task #7040] Work on tcp_enqueue, bill, 2009/02/02
- Re: [lwip-devel] Re: [task #7040] Work on tcp_enqueue, address@hidden, 2009/02/02
- RE: [lwip-devel] Re: [task #7040] Work on tcp_enqueue, bill, 2009/02/02
- Re: [lwip-devel] Re: [task #7040] Work on tcp_enqueue, address@hidden, 2009/02/02
- RE: [lwip-devel] Re: [task #7040] Work on tcp_enqueue, bill, 2009/02/02
- Re: [lwip-devel] Re: [task #7040] Work on tcp_enqueue, address@hidden, 2009/02/02
- RE: [lwip-devel] Re: [task #7040] Work on tcp_enqueue, bill, 2009/02/03
- Re: [lwip-devel] Re: [task #7040] Work on tcp_enqueue,
Jonathan Larmour <=
Re: [lwip-devel] Re: [task #7040] Work on tcp_enqueue, Jonathan Larmour, 2009/02/01
[lwip-devel] Re: [task #7040] Work on tcp_enqueue, Jakob Stoklund Olesen, 2009/02/01