aboutsummaryrefslogtreecommitdiffstats
path: root/libavcodec/mpegvideodsp.h
diff options
context:
space:
mode:
authorWan-Teh Chang <wtc@google.com>2016-12-09 09:54:47 -0800
committerAnton Khirnov <anton@khirnov.net>2016-12-14 11:16:51 +0100
commit343e2833994655c252d5236a3394bf6db7a4d8b1 (patch)
tree3af18f9a15347644bac26984b330ce0e9e37ff3b /libavcodec/mpegvideodsp.h
parente94b9313b21c3d91a36ef064f7fe3e867616f47f (diff)
downloadffmpeg-343e2833994655c252d5236a3394bf6db7a4d8b1.tar.gz
pthread_frame: use better memory orders for frame progress
This improves commit 59c70227405c214b29971e6272f3a3ff6fcce3d0. In ff_thread_report_progress(), the fast code path can load progress[field] with the relaxed memory order, and the slow code path can store progress[field] with the release memory order. These changes are mainly intended to avoid confusion when one inspects the source code. They are unlikely to have measurable performance improvement. ff_thread_report_progress() and ff_thread_await_progress() form a pair. ff_thread_await_progress() reads progress[field] with the acquire memory order (in the fast code path). Therefore, one expects to see ff_thread_report_progress() write progress[field] with the matching release memory order. In the fast code path in ff_thread_report_progress(), the atomic load of progress[field] doesn't need the acquire memory order because the calling thread is trying to make the data it just decoded visible to the other threads, rather than trying to read the data decoded by other threads. In ff_thread_get_buffer(), initialize progress[0] and progress[1] using atomic_init(). Signed-off-by: Wan-Teh Chang <wtc@google.com> Signed-off-by: Anton Khirnov <anton@khirnov.net>
Diffstat (limited to 'libavcodec/mpegvideodsp.h')
0 files changed, 0 insertions, 0 deletions