[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lwip-users] Multi-threaded socket access once again
From: |
Fabian Koch |
Subject: |
Re: [lwip-users] Multi-threaded socket access once again |
Date: |
Fri, 18 Jul 2014 12:55:27 +0000 |
Hey Steffen,
<insert the usual "not supported answer" here first>
Having said that, it seems like an okay setup if there are no other unexpected
accesses.
For example if another task closes the socket while your receive task is in the
select() you'll also be in trouble.
For our adaptation we modified LwIP to silently exit the select() call if that
happens but in the official release, is runs into assertions.
The whole ordeal of "access sockets from multiple tasks" is a big topic in my
opinion and not something that LwIP can hide from.
I know the construct of the single op_completed semaphore and the mboxes is one
of the main problems behind not being able to support multiple tasks, but the
argument of no longer being light-weight is not true if we make all the
necessary changes optional and flexible.
Cheers,
Fabian