From: Hans Verkuil <hverkuil@xs4all.nl>
To: Benjamin Gaignard <benjamin.gaignard@collabora.com>, mchehab@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
kernel@collabora.com
Subject: Re: [PATCH v17 8/8] media: verisilicon: Support deleting buffers on capture queue
Date: Wed, 24 Jan 2024 16:44:45 +0100 [thread overview]
Message-ID: <7f40af24-79a8-466c-8906-7104988124fb@xs4all.nl> (raw)
In-Reply-To: <1cd7c504-c384-4c9c-bedd-79cd8aed8484@collabora.com>
On 24/01/2024 16:35, Benjamin Gaignard wrote:
>
> Le 24/01/2024 à 13:52, Hans Verkuil a écrit :
>> On 19/01/2024 10:49, Benjamin Gaignard wrote:
>>> Allow to delete buffers on capture queue because it the one which
>>> own the decoded buffers. After a dynamic resolution change lot of
>>> them could remain allocated but won't be used anymore so deleting
>>> them save memory.
>>> Do not add this feature on output queue because the buffers are
>>> smaller, fewer and always recycled even after a dynamic resolution
>>> change.
>>>
>>> Signed-off-by: Benjamin Gaignard <benjamin.gaignard@collabora.com>
>>> ---
>>> drivers/media/platform/verisilicon/hantro_drv.c | 1 +
>>> drivers/media/platform/verisilicon/hantro_v4l2.c | 1 +
>>> 2 files changed, 2 insertions(+)
>>>
>>> diff --git a/drivers/media/platform/verisilicon/hantro_drv.c b/drivers/media/platform/verisilicon/hantro_drv.c
>>> index db3df6cc4513..f6b0a676a740 100644
>>> --- a/drivers/media/platform/verisilicon/hantro_drv.c
>>> +++ b/drivers/media/platform/verisilicon/hantro_drv.c
>>> @@ -248,6 +248,7 @@ queue_init(void *priv, struct vb2_queue *src_vq, struct vb2_queue *dst_vq)
>>> dst_vq->timestamp_flags = V4L2_BUF_FLAG_TIMESTAMP_COPY;
>>> dst_vq->lock = &ctx->dev->vpu_mutex;
>>> dst_vq->dev = ctx->dev->v4l2_dev.dev;
>>> + src_vq->supports_delete_bufs = true;
>> As I mentioned, I remain unconvinced by this. It is just making the API inconsistent
>> since if you support delete_bufs, then why support it for one queue only and not both?
>
> Because the both queues don't handle the same type of data.
> For example for a stateless decoder, for me, it makes sense to allow delete decoded frames
> if they won't be used anymore but that won't makes sense for bitstream buffers.
But is there any reason why you wouldn't support this feature? We support VIDIOC_CREATE_BUFS
as well, even though most drivers do not need it, but it is cheap to add.
Deleting buffers is a generic feature, and I don't see why you wouldn't just offer it
for both queues.
Regards,
Hans
>
>>
>>> return vb2_queue_init(dst_vq);
>>> }
>>> diff --git a/drivers/media/platform/verisilicon/hantro_v4l2.c b/drivers/media/platform/verisilicon/hantro_v4l2.c
>>> index 941fa23c211a..34eab90e8a42 100644
>>> --- a/drivers/media/platform/verisilicon/hantro_v4l2.c
>>> +++ b/drivers/media/platform/verisilicon/hantro_v4l2.c
>>> @@ -756,6 +756,7 @@ const struct v4l2_ioctl_ops hantro_ioctl_ops = {
>>> .vidioc_dqbuf = v4l2_m2m_ioctl_dqbuf,
>>> .vidioc_prepare_buf = v4l2_m2m_ioctl_prepare_buf,
>>> .vidioc_create_bufs = v4l2_m2m_ioctl_create_bufs,
>>> + .vidioc_delete_bufs = v4l2_m2m_ioctl_delete_bufs,
>>> .vidioc_expbuf = v4l2_m2m_ioctl_expbuf,
>>> .vidioc_subscribe_event = v4l2_ctrl_subscribe_event,
>> In my view setting vidioc_delete_bufs should enable this feature, and if
>> for some strange reason only one queue support it, then make a wrapper
>> callback that returns an error when used with the wrong queue.
>>
>> Also note that patch 6/8 never checks for q->supports_delete_bufs in
>> vb2_core_delete_bufs(), which is wrong!
>
> I will fix that in next version.
> Regards,
> Benjamin
>
>>
>> Regards,
>>
>> Hans
>>
next prev parent reply other threads:[~2024-01-24 15:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 9:49 [PATCH v17 0/8] Add DELETE_BUF ioctl Benjamin Gaignard
2024-01-19 9:49 ` [PATCH v17 1/8] videobuf2: Add min_reqbufs_allocation field to vb2_queue structure Benjamin Gaignard
2024-01-24 11:31 ` Hans Verkuil
2024-01-19 9:49 ` [PATCH v17 2/8] media: test-drivers: Set REQBUFS minimum number of buffers Benjamin Gaignard
2024-01-19 9:49 ` [PATCH v17 3/8] media: core: Rework how create_buf index returned value is computed Benjamin Gaignard
2024-01-24 11:20 ` Hans Verkuil
2024-01-19 9:49 ` [PATCH v17 4/8] media: core: Add bitmap manage bufs array entries Benjamin Gaignard
2024-01-24 11:52 ` Hans Verkuil
2024-01-19 9:49 ` [PATCH v17 5/8] media: core: Free range of buffers Benjamin Gaignard
2024-01-19 9:49 ` [PATCH v17 6/8] media: v4l2: Add DELETE_BUFS ioctl Benjamin Gaignard
2024-01-24 12:33 ` Hans Verkuil
2024-01-24 12:59 ` Hans Verkuil
2024-01-24 15:35 ` Benjamin Gaignard
2024-01-24 15:46 ` Hans Verkuil
2024-01-19 9:49 ` [PATCH v17 7/8] media: v4l2: Add mem2mem helpers for " Benjamin Gaignard
2024-01-19 9:49 ` [PATCH v17 8/8] media: verisilicon: Support deleting buffers on capture queue Benjamin Gaignard
2024-01-24 12:52 ` Hans Verkuil
2024-01-24 15:35 ` Benjamin Gaignard
2024-01-24 15:44 ` Hans Verkuil [this message]
2024-01-25 9:27 ` Benjamin Gaignard
2024-01-25 9:50 ` Hans Verkuil
2024-01-25 16:27 ` Nicolas Dufresne
2024-01-26 9:17 ` Hans Verkuil
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=7f40af24-79a8-466c-8906-7104988124fb@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=benjamin.gaignard@collabora.com \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.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
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;
as well as URLs for NNTP newsgroup(s).