[Top][All Lists]

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

[lwip-devel] [patch #5914] Move sockopt processing into tcpip_thread

From: Simon Goldschmidt
Subject: [lwip-devel] [patch #5914] Move sockopt processing into tcpip_thread
Date: Fri, 04 May 2007 09:49:21 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv: Gecko/20070309 Firefox/

Follow-up Comment #6, patch #5914 (project lwip):

>so, if the issue if for thread-safe, I suppose it is also true for netconn,
right? And I suppose that a netconn user directly access to pcb fields if he
need these optiions?

Yes, I think so, too. But I don't really want to introduce new netconn API
functions as long as nobody uses them...

>About "calls tcpip_callback() maybe with automatic mbox synchronization",
isn't it finally the same thing that tcpip_apimsg ?

Yes it is like that, but when integrating setsockopt into api messages, we
would have to introduce yet another type of api msg.

>Can you tell me more about the issue you want to fix ?

Huh? What do you mean? I'm trying to make lwIP sockets API more thread-safe,
if that's what you mean?


Reply to this item at:


  Nachricht geschickt von/durch Savannah

reply via email to

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