On Mon, Jul 1, 2024 at 10:13 PM Nuo Mi wrote:
>
>
> On Mon, Jul 1, 2024 at 10:00 PM Zhao Zhili wrote:
>
>>
>>
>> > On Jul 1, 2024, at 21:14, Nuo Mi wrote:
>> >
>> > On Sun, Jun 30, 2024 at 6:45 PM Zhao Zhili
>> wrote:
>> >
>> >> From: Zhao Zhili
>> >>
>> >> ---
>> >> The code can be simplifie
On Mon, Jul 1, 2024 at 10:00 PM Zhao Zhili wrote:
>
>
> > On Jul 1, 2024, at 21:14, Nuo Mi wrote:
> >
> > On Sun, Jun 30, 2024 at 6:45 PM Zhao Zhili
> wrote:
> >
> >> From: Zhao Zhili
> >>
> >> ---
> >> The code can be simplified by always creating mutex/cond. I'm not sure
> >> it worth the ov
> On Jul 1, 2024, at 21:14, Nuo Mi wrote:
>
> On Sun, Jun 30, 2024 at 6:45 PM Zhao Zhili wrote:
>
>> From: Zhao Zhili
>>
>> ---
>> The code can be simplified by always creating mutex/cond. I'm not sure
>> it worth the overhead. Please note !HAVE_THREADS don't have the same
>> problem since
On Sun, Jun 30, 2024 at 6:45 PM Zhao Zhili wrote:
> From: Zhao Zhili
>
> ---
> The code can be simplified by always creating mutex/cond. I'm not sure
> it worth the overhead. Please note !HAVE_THREADS don't have the same
> problem since it has mock implementation of ff_mutex_lock/unlock.
>
Hi Zh