diff options
| author | Ronald S. Bultje <rsbultje@gmail.com> | 2017-04-03 10:24:05 -0400 |
|---|---|---|
| committer | Michael Niedermayer <michael@niedermayer.cc> | 2017-04-13 02:29:26 +0200 |
| commit | f4f3bf3c94a9aa485c09d0c03d68ca79a4785866 (patch) | |
| tree | 91c033db9b6fd121b40c46cd0ef4a5b96cb01eda /libavcodec/r210enc.c | |
| parent | 6557ea8e2bd768f5d82bce0fab28262437a292bf (diff) | |
| download | ffmpeg-f4f3bf3c94a9aa485c09d0c03d68ca79a4785866.tar.gz | |
pthread_frame: allow per-field ThreadFrame owners.
This tries to handle cases where separate invocations of decode_frame()
(each running in separate threads) write to respective fields in the
same AVFrame->data[]. Having per-field owners makes interaction between
readers (the referencing thread) and writers (the decoding thread)
slightly more optimal if both accesses are field-based, since they will
use the respective producer's thread objects (mutex/cond) instead of
sharing the thread objects of the first field's producer.
In practice, this fixes the following tsan-warning in fate-h264:
WARNING: ThreadSanitizer: data race (pid=21615)
Read of size 4 at 0x7d640000d9fc by thread T2 (mutexes: write M1006):
#0 ff_thread_report_progress pthread_frame.c:569 (ffmpeg:x86_64+0x100f7cf54)
[..]
Previous write of size 4 at 0x7d640000d9fc by main thread (mutexes: write M1004):
#0 update_context_from_user pthread_frame.c:335 (ffmpeg:x86_64+0x100f81abb)
(cherry picked from commit 083300bea935d125b83f60d7030f78a7ffb0f3df)
Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
Diffstat (limited to 'libavcodec/r210enc.c')
0 files changed, 0 insertions, 0 deletions