RE: [lwip-users] BasicWeb.c behavior

[Pettinato, Jim]

I think the issue they're expressing is that the PCB memory pool's associated 
stats.err member gets incremented in this case even though the fail/kill/retry 
sequence ends up being successful?

-----Original Message-----
From: address@hidden [mailto:address@hidden On Behalf Of Jonathan Larmour
Sent: Friday, February 08, 2008 3:03 PM
To: Mailing list for lwIP users
Subject: Re: [lwip-users] BasicWeb.c behavior

Bill Auerbach wrote:
> 
> In tcp_alloc, if memp_malloc returns NULL then tcp_kill_timewait is 
> used to kill an old PCB.  I would think the error should be reversed 
> when the next memp_malloc succeeds, or, we need a memp_malloc_try 
> which doesn't count the error on a fail, but allocates one if it can.

I'm not sure what you mean here. The current code looks ok to me? It retries 
the memp_malloc straight after killing off a socket in timewait.

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.
Visit us @ Embedded World 2008, Nürnberg, Germany, 26-28 Feb:Stand 11-336
------["Si fractum non sit, noli id reficere"]------       Opinions==mine


_______________________________________________
lwip-users mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/lwip-users