[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-users] Re: [lwip] threads, semaphores and raw interface question
From: |
leon . woestenberg |
Subject: |
[lwip-users] Re: [lwip] threads, semaphores and raw interface question |
Date: |
Wed, 08 Jan 2003 21:54:32 -0000 |
Hello Adam,
OK, that clears things up for me.
An additional question, just to be sure I understand the consequences
of using the raw API:
Does this mean the messaging (mail box) calls can be left empty as well?
I Under pre-0.5 lwIP, the minimal single-threaded sys_arch merely has to
implement
Leon Woestenberg
Axon Digital Design
Phone: +31 13 511 6666
Fax: +31 13 511 4151
web: www.axon.tv
The semaphore calls in the sys_arch can be implemented as empty functions
in
the single threaded case. The reason for using them in the code (memp.c and
mem.c) is that the code should work in the multithreaded case as well. The
memory pools and the heap memory are shared resources so they have to be
protected by semaphores. In a single threaded environment, this protection
isn't necessary so the sys_sem_ functions can be left empty.
[This message was sent through the lwip discussion list.]
- [lwip-users] Re: [lwip] threads, semaphores and raw interface question,
leon . woestenberg <=