From: Nicolas Dufresne <nicolas@ndufresne.ca>
To: "Jackson.lee" <jackson.lee@chipsnmedia.com>,
mchehab@kernel.org, hverkuil-cisco@xs4all.nl,
sebastian.fricke@collabora.com, bob.beckett@collabora.com,
dafna.hirschfeld@collabora.com
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
lafley.kim@chipsnmedia.com, b-brnich@ti.com, hverkuil@xs4all.nl,
nas.chung@chipsnmedia.com
Subject: Re: [RESEND PATCH v0 0/3] Performance improvement of decoder
Date: Wed, 02 Apr 2025 11:44:23 -0400 [thread overview]
Message-ID: <9f22aaa07b1fa11e7e1dee35598bafe5a3461ea7.camel@ndufresne.ca> (raw)
In-Reply-To: <20250319035034.111-1-jackson.lee@chipsnmedia.com>
Hi,
Le mercredi 19 mars 2025 à 12:50 +0900, Jackson.lee a écrit :
> From: Jackson Lee <jackson.lee@chipsnmedia.com>
>
> The wave5 codec driver is a stateful encoder/decoder.
> The following patches is for improving decoder performance.
>
> v4l2-compliance results:
> ========================
>
> v4l2-compliance 1.28.1-5233, 64 bits, 64-bit time_t
>
> Buffer ioctls:
> warn: v4l2-test-buffers.cpp(693): VIDIOC_CREATE_BUFS not supported
> warn: v4l2-test-buffers.cpp(693): VIDIOC_CREATE_BUFS not supported
> test VIDIOC_REQBUFS/CREATE_BUFS/QUERYBUF: OK
> test CREATE_BUFS maximum buffers: OK
> test VIDIOC_EXPBUF: OK
> test Requests: OK (Not Supported)
>
> Total for wave5-dec device /dev/video0: 46, Succeeded: 46, Failed: 0, Warnings: 2
> Total for wave5-enc device /dev/video1: 46, Succeeded: 46, Failed: 0, Warnings: 0
>
> Fluster test results:
> =====================
>
> Running test suite JCT-VC-HEVC_V1 with decoder GStreamer-H.265-V4L2-Gst1.0 Using 1 parallel job(s)
> Ran 133/147 tests successfully in 68.517 secs
>
> (1 test fails because of not supporting to parse multi frames, 1 test fails because of a missing frame and slight corruption,
> 2 tests fail because of sizes which are incompatible with the IP, 11 tests fail because of unsupported 10 bit format)
>
> Running test suite JVT-AVC_V1 with decoder GStreamer-H.264-V4L2-Gst1.0 Using 1 parallel job(s)
> Ran 78/135 tests successfully in 35.015 secs
I'd be more confortable if I could get test report using 2 or 3
parallel instances.
Also, have you conducted manual "seek" tests, and stress tested the
dynamic resolution changes ? We don't have automated tests for these
anywhere yet.
Nicolas
>
> (57 fail because the hardware is unable to decode MBAFF / FMO / Field / Extended profile streams.)
>
>
> Jackson Lee (3):
> media: chips-media: wave5: Improve performance of decoder
> media: chips-media: wave5: Reduce high CPU load
> media: chips-media: wave5: Fix Null reference while testing fluster
>
> .../platform/chips-media/wave5/wave5-helper.c | 10 +-
> .../chips-media/wave5/wave5-vpu-dec.c | 361 ++++++++++--------
> .../chips-media/wave5/wave5-vpu-enc.c | 8 +-
> .../platform/chips-media/wave5/wave5-vpu.c | 69 +++-
> .../platform/chips-media/wave5/wave5-vpuapi.c | 25 +-
> .../platform/chips-media/wave5/wave5-vpuapi.h | 12 +-
> 6 files changed, 307 insertions(+), 178 deletions(-)
next prev parent reply other threads:[~2025-04-02 15:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 3:50 Jackson.lee
2025-03-19 3:50 ` [RESEND PATCH v0 1/3] media: chips-media: wave5: Improve performance " Jackson.lee
2025-04-02 18:02 ` Nicolas Dufresne
2025-04-04 4:16 ` jackson.lee
2025-04-04 16:00 ` Nicolas Dufresne
2025-04-07 0:37 ` jackson.lee
2025-03-19 3:50 ` [RESEND PATCH v0 2/3] media: chips-media: wave5: Reduce high CPU load Jackson.lee
2025-03-19 3:50 ` [RESEND PATCH v0 3/3] media: chips-media: wave5: Fix Null reference while testing fluster Jackson.lee
2025-04-02 15:44 ` Nicolas Dufresne [this message]
2025-04-03 1:29 ` [RESEND PATCH v0 0/3] Performance improvement of decoder jackson.lee
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=9f22aaa07b1fa11e7e1dee35598bafe5a3461ea7.camel@ndufresne.ca \
--to=nicolas@ndufresne.ca \
--cc=b-brnich@ti.com \
--cc=bob.beckett@collabora.com \
--cc=dafna.hirschfeld@collabora.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=hverkuil@xs4all.nl \
--cc=jackson.lee@chipsnmedia.com \
--cc=lafley.kim@chipsnmedia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nas.chung@chipsnmedia.com \
--cc=sebastian.fricke@collabora.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®