Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v4] vvcdec: add thread executor
Date: Tue, 22 Aug 2023 09:23:46 -0300
Message-ID: <89dcb600-a8bc-b545-9504-a9afe869388b@gmail.com> (raw)
In-Reply-To: <CAFXK13eLtsuq=cVQLVHpmK3Xm-03fcs1A-60factaN7FybQW3w@mail.gmail.com>

On 8/22/2023 9:03 AM, Nuo Mi wrote:
> On Thu, Aug 17, 2023 at 12:42 AM Rémi Denis-Courmont <remi@remlab.net>
> wrote:
> 
>> Le tiistaina 15. elokuuta 2023, 17.50.13 EEST Nuo Mi a écrit :
>>> The executor design pattern was inroduced by java
>>> <
>> https://docs.oracle.com/en/java/javase/20/docs/api/java.base/java/util/conc
>>> urrent/Executor.html> it also adapted by python
>>> <https://docs.python.org/3/library/concurrent.futures.html>
>>> Compared to handcrafted thread pool management, it greatly simplifies the
>>> thread code. ---
>>>   libavutil/Makefile   |   2 +
>>>   libavutil/executor.c | 201 +++++++++++++++++++++++++++++++++++++++++++
>>>   libavutil/executor.h |  67 +++++++++++++++
>>>   3 files changed, 270 insertions(+)
>>>   create mode 100644 libavutil/executor.c
>>>   create mode 100644 libavutil/executor.h
>>>
>>> diff --git a/libavutil/Makefile b/libavutil/Makefile
>>> index 7828c94dc5..4711f8cde8 100644
>>> --- a/libavutil/Makefile
>>> +++ b/libavutil/Makefile
>>> @@ -31,6 +31,7 @@ HEADERS = adler32.h
>>
>>>               \ encryption_info.h
>>
>>>   \ error.h                                                       \
>> eval.h
>>>                                                       \ +
>>> executor.h                                                    \ fifo.h
>>
>>>                                                    \ file.h
>>
>>>                                        \ frame.h
>>
>>>                            \ @@ -127,6 +128,7 @@ OBJS = adler32.o
>>
>>>                                              \ encryption_info.o
>>
>>>                                     \ error.o
>>
>>>                            \ eval.o
>>
>>>                   \ +       executor.o
>>
>>>                  \ fifo.o
>>
>>>         \ file.o
>>   \
>>> file_open.o                                                      \ diff
>>> --git a/libavutil/executor.c b/libavutil/executor.c
>>> new file mode 100644
>>> index 0000000000..6b47ba0bf2
>>> --- /dev/null
>>> +++ b/libavutil/executor.c
>>> @@ -0,0 +1,201 @@
>>> +/*
>>> + * Copyright (C) 2023 Nuo Mi
>>> + *
>>> + * This file is part of FFmpeg.
>>> + *
>>> + * FFmpeg is free software; you can redistribute it and/or
>>> + * modify it under the terms of the GNU Lesser General Public
>>> + * License as published by the Free Software Foundation; either
>>> + * version 2.1 of the License, or (at your option) any later version.
>>> + *
>>> + * FFmpeg is distributed in the hope that it will be useful,
>>> + * but WITHOUT ANY WARRANTY; without even the implied warranty of
>>> + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
>>> + * Lesser General Public License for more details.
>>> + *
>>> + * You should have received a copy of the GNU Lesser General Public
>>> + * License along with FFmpeg; if not, write to the Free Software
>>> + * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
>> 02110-1301
>>> USA + */
>>> +#include "internal.h"
>>> +#include "mem.h"
>>> +#include "thread.h"
>>> +
>>> +#include "executor.h"
>>> +
>>> +#if !HAVE_THREADS
>>> +#define pthread_create(t, a, s, ar)     0
>>
>> Err, this should probably return an error value, e.g. ENOSYS or ENOTSUP.
>>
>>> +#define pthread_join(t, r)              do {} while(0)
>>
>> ...and this should be an unreachable(), assert(0), abort() or something
>> along
>> those lines.
>>
>>> +
>>> +#define pthread_cond_init(c, a)         0
>>> +#define pthread_cond_broadcast(c)       do {} while(0)
>>> +#define pthread_cond_signal(c)          do {} while(0)
>>> +#define pthread_cond_wait(c, m)         do {} while(0)
>>> +#define pthread_cond_destroy(c)         do {} while(0)
>>> +
>>> +#define pthread_mutex_init(m, a)        0
>>> +#define pthread_mutex_lock(l)           do {} while(0)
>>> +#define pthread_mutex_unlock(l)         do {} while(0)
>>> +#define pthread_mutex_destroy(l)        do {} while(0)
>>> +#endif
>>> +
>>> +typedef struct ThreadInfo {
>>> +    AVExecutor *e;
>>> +    pthread_t thread;
>>
>> Does this even work if !HAVE_THREAD ?
> 
> Yes. The definition provided by the following include chain:
>   "mem.h"->"avutil.h"->"common.h"->"<stdlib.h>"->"<sys/types.h>"->"<bits/pthreadtypes.h>"

Why would bits/pthreadtypes.h be available if there's no pthreads?
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  reply	other threads:[~2023-08-22 12:23 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230707140540.10279-1-nuomi2021@gmail.com>
2023-07-07 14:05 ` [FFmpeg-devel] [PATCH v2 01/14] " Nuo Mi
2023-07-08 21:51   ` Michael Niedermayer
2023-07-10  7:41     ` Nuo Mi
2023-07-16  6:28       ` Nuo Mi
2023-07-17 22:13         ` Michael Niedermayer
2023-07-18 11:53           ` Nuo Mi
2023-07-18 14:55             ` Michael Niedermayer
2023-07-14 22:38   ` Michael Niedermayer
2023-07-16  7:07     ` Nuo Mi
2023-07-19 13:13   ` [FFmpeg-devel] [PATCH v3] " Nuo Mi
2023-07-19 13:19     ` Nuo Mi
2023-08-14 16:46     ` Michael Niedermayer
2023-08-15 14:53       ` Nuo Mi
2023-08-15 14:50     ` [FFmpeg-devel] [PATCH v4] " Nuo Mi
2023-08-16 16:35       ` Michael Niedermayer
2023-08-22 13:34         ` Nuo Mi
2023-08-16 16:42       ` Rémi Denis-Courmont
2023-08-18 15:54         ` James Almer
2023-08-22 12:03         ` Nuo Mi
2023-08-22 12:23           ` James Almer [this message]
2023-08-22 12:30             ` Nuo Mi
2023-08-22 12:32               ` James Almer
2023-08-22 13:34                 ` Nuo Mi
2023-08-18 16:17       ` James Almer
2023-08-19 13:09         ` James Almer
2023-08-22 12:09           ` Nuo Mi
2023-08-22 12:20         ` Nuo Mi
2023-08-22 13:32       ` [FFmpeg-devel] [PATCH v5] " Nuo Mi
2023-08-28 17:06         ` Michael Niedermayer
2023-08-29 13:07           ` Nuo Mi
2023-08-29 12:59         ` [FFmpeg-devel] [PATCH v6] " Nuo Mi
2023-07-07 14:05 ` [FFmpeg-devel] [PATCH v2 02/14] vvcdec: add vvc decoder stub Nuo Mi
2023-07-07 14:05 ` [FFmpeg-devel] [PATCH v2 03/14] vvcdec: add sps, pps, sh parser Nuo Mi
2023-07-07 14:28   ` James Almer
2023-07-07 15:48     ` Nuo Mi
2023-07-07 16:29       ` James Almer
2023-07-10  7:46         ` Nuo Mi
2023-07-07 14:05 ` [FFmpeg-devel] [PATCH v2 04/14] vvcdec: add cabac decoder Nuo Mi
2023-07-07 14:05 ` [FFmpeg-devel] [PATCH v2 05/14] vvcdec: add reference management Nuo Mi
2023-07-07 14:05 ` [FFmpeg-devel] [PATCH v2 06/14] vvcdec: add motion vector decoder Nuo Mi
2023-07-07 14:05 ` [FFmpeg-devel] [PATCH v2 07/14] vvcdec: add inter prediction Nuo Mi
2023-07-07 14:05 ` [FFmpeg-devel] [PATCH v2 08/14] vvcdec: add inv transform 1d Nuo Mi
2023-07-07 14:05 ` [FFmpeg-devel] [PATCH v2 09/14] vvcdec: add intra prediction Nuo Mi
2023-07-07 14:05 ` [FFmpeg-devel] [PATCH v2 10/14] vvcdec: add LMCS, Deblocking, SAO, and ALF filters Nuo Mi
2023-07-07 14:05 ` [FFmpeg-devel] [PATCH v2 11/14] vvcdec: add dsp init and inv transform Nuo Mi
2023-07-07 14:05 ` [FFmpeg-devel] [PATCH v2 12/14] vvcdec: add CTU parser Nuo Mi
2023-07-07 14:05 ` [FFmpeg-devel] [PATCH v2 13/14] vvcdec: add CTU thread logical Nuo Mi
2023-07-08 21:41   ` Michael Niedermayer
2023-07-09  1:04     ` Andreas Rheinhardt
2023-07-10  7:45       ` Nuo Mi
2023-07-10 15:04     ` Rémi Denis-Courmont
2023-07-11 17:28       ` Michael Niedermayer
2023-07-07 14:05 ` [FFmpeg-devel] [PATCH v2 14/14] vvcdec: add full vvc decoder Nuo Mi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=89dcb600-a8bc-b545-9504-a9afe869388b@gmail.com \
    --to=jamrial@gmail.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git