ok, I would use SYS_ARCH_PROTECT in my next app version . thanks a lot,
Joe.
--
View this message in context:
http://lwip.100.n7.nabble.com/LwIP-multithread-select-mode-problems-tp26561p26674.html
Sent from the lwip-users mailing list archive at Nabble.com.
_
See responses in-line
Joel
On Jun 24, 2016, at 09:31 PM, lampo wrote:
thanks a lot.
now I use *recv*, *send*, *close* apis in the same thread per one
socket, that means each client socket occupy a new thread, and each of
them calles *select*, *recv*, *send*, *close* .
I'm wondering is th
thanks a lot.
now I use *recv*, *send*, *close* apis in the same thread per one
socket, that means each client socket occupy a new thread, and each of
them calles *select*, *recv*, *send*, *close* .
I'm wondering is this usage still so called multi-threaded environment
? can I
Yes you need SYS_ARCH_PROTECT in a multi-threaded environment. Whether or not
you use SYS_LIGHTWEIGHT_PROT just controls whether the function prototypes are
produced and used in SYS_ARCH_PROTECT:
#define SYS_ARCH_DECL_PROTECT(lev) sys_prot_t lev
#define SYS_ARCH_PROTECT(lev) lev = sys_arch_p
Jin,
please don't hijack other people's threads.
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
thank you ! Joel
I still want to know if /SYS_ARCH_PROTECT/ is a must in multiple
threads environment?
I see a lot of /SYS_ARCH_PROTECT/ in select() and other sockets apis.
But when I set /SYS_LIGHATWEIGHT_PROT/ to 1 to use *SYS_ARCH_PROTECT*, the
applicaton run into hardfault or stack
ent: Thursday, June 23, 2016 9:03 PM
To: Mailing list for lwIP users
Subject: Re: [lwip-users] LwIP multithread select mode problems
Hi Noam,
I did not expect any replies, but you did. I appreciate your suggestions.
I am using Socket using Lwip and do not have any issues to handle semaphore,
mutex,
oking for a job, use the time in between to learn new skills.
> Learn some JS, XML,
>
> JSON, HTML etc…
>
>
>
>
>
> Good luck,
>
> Noam.
>
> *From:* lwip-users [mailto:lwip-users-bounces+noam=silrd....@nongnu.org] *On
> Behalf Of *Jin Won Seo
> *Sent:* Th
: [lwip-users] LwIP multithread select mode problems
Sorry for irrelevant reply, but I am so frustrated to find a job.
I used Lwip 1.4.1 in my project + RTOS, but ... almost nothing I can find.
Is this industry dead? These skill sets are not useful?
On Thu, Jun 23, 2016 at 7:33 AM, Joel Cunningham
Sorry for irrelevant reply, but I am so frustrated to find a job.
I used Lwip 1.4.1 in my project + RTOS, but ... almost nothing I can find.
Is this industry dead? These skill sets are not useful?
On Thu, Jun 23, 2016 at 7:33 AM, Joel Cunningham
wrote:
> Hi,
>
> select() can be used by multip
Hi,
select() can be used by multiple threads at the same time and you can even have
the same sockets in multiple calls and it will be safe. The limitation comes
from trying to use the same sockets from multiple simultaneous threads in other
socket APIs (select is the exception, simultaneous
hello,
can someone help me with multithread problem ?
we use lwip 1.4.1 in PLC products, and if it live through long time(1 month
for example) testing in industry use,
I will back here to report.
*our problem*
we use multithread select mode in our system, and it "seems" it's ok till
now(1 days
12 matches
Mail list logo
