[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lwip-devel] Can we change sys_arch_sem_wait's timeout meaning?
From: |
address@hidden |
Subject: |
Re: [lwip-devel] Can we change sys_arch_sem_wait's timeout meaning? |
Date: |
Tue, 17 Aug 2021 20:44:44 +0200 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 |
Am 21.07.2021 um 14:06 schrieb 罗勇刚(Yonggang Luo):
>
>
> On Wed, Jul 21, 2021 at 5:44 PM Hans Petter Selasky <hps@selasky.org
> <mailto:hps@selasky.org>> wrote:
>>
>> On 7/5/21 12:11 PM, 罗勇刚(Yonggang Luo) wrote:
>> > In most os, timeout == 0 means waiting no time
>> > timeout ==-1 means wait infinite.
>> > Or we added a new API and deprecating sys_arch_sem_wait?
>>
>> Hi,
>>
>> Can you tell more about which OS uses 0 for infinite timeout?
>
> Most OS use 0 for zero timeout(no wait).
> But in lwip, sys_arch_sem_wait(0) means infinite timeout
Well, yes, the current state is not ideal. But I con't think that it is
worth the effort of breaking all existing ports by requiring them to
implement a new function where the timeout parameter has changed its
meaning.
Regards,
Simon
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [lwip-devel] Can we change sys_arch_sem_wait's timeout meaning?,
address@hidden <=