[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-devel] [task #6994] Redesign Socket Layer with LWIP_TCPIP_CORE_LOC

From: Simon Goldschmidt
Subject: [lwip-devel] [task #6994] Redesign Socket Layer with LWIP_TCPIP_CORE_LOCKING
Date: Sat, 09 Jun 2007 16:29:23 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv: Gecko/20070515 Firefox/

Follow-up Comment #1, task #6994 (project lwip):

> For this, perhaps alternative api_msg2.c file will be better to avoid

Why not include all functions in 'socket2.c'? We don't have to seperate the
code into 'application thread code' and 'tcpip_thread code' like with
api_lib/api_msg. Just lock the core and go on with the code...

We wouldn't even need the tcpip_thread any more. Simply lock and call into
the core from your RX-thread (if it's not done in interrupt context).

Even timeouts can be done easier: Either in an extra thread or in the
RX-thread. Both version would remove the need for a per-thread timeout we
have now. That way, sys_sem_wait and sys_mbox_fetch get smaller, too.

In a further step I'd like to introduce finer graned locking so that e.g.
only tcp and its pcb is locked while processing a received tcp segment. This
could help prioritizing some connections over others.


Reply to this item at:


  Nachricht geschickt von/durch Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]