From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/hevc_ps: allocate only the required HEVCHdrParams within a VPS
Date: Thu, 21 Mar 2024 09:11:16 -0300
Message-ID: <78d1ee1d-9617-4757-833d-12719831862d@gmail.com> (raw)
In-Reply-To: <DU0P250MB0747E5025DC807F7540487548F322@DU0P250MB0747.EURP250.PROD.OUTLOOK.COM>
On 3/21/2024 8:15 AM, Andreas Rheinhardt wrote:
> James Almer:
>> Signed-off-by: James Almer <jamrial@gmail.com>
>> ---
>> libavcodec/hevc_ps.c | 17 +++++++++++++++--
>> libavcodec/hevc_ps.h | 2 +-
>> libavcodec/vulkan_hevc.c | 2 +-
>> 3 files changed, 17 insertions(+), 4 deletions(-)
>>
>> diff --git a/libavcodec/hevc_ps.c b/libavcodec/hevc_ps.c
>> index 20ceb09829..d3edc0810d 100644
>> --- a/libavcodec/hevc_ps.c
>> +++ b/libavcodec/hevc_ps.c
>> @@ -442,13 +442,21 @@ static int decode_hrd(GetBitContext *gb, int common_inf_present,
>> return 0;
>> }
>>
>> +static void uninit_vps(FFRefStructOpaque opaque, void *obj)
>> +{
>> + HEVCVPS *vps = obj;
>> +
>> + for (int i = 0; i < vps->vps_num_hrd_parameters; i++)
>> + ff_refstruct_unref(&vps->hdr[i]);
>> +}
>> +
>> int ff_hevc_decode_nal_vps(GetBitContext *gb, AVCodecContext *avctx,
>> HEVCParamSets *ps)
>> {
>> int i,j;
>> int vps_id = 0;
>> ptrdiff_t nal_size;
>> - HEVCVPS *vps = ff_refstruct_allocz(sizeof(*vps));
>> + HEVCVPS *vps = ff_refstruct_alloc_ext(sizeof(*vps), 0, NULL, uninit_vps);
>>
>> if (!vps)
>> return AVERROR(ENOMEM);
>> @@ -538,12 +546,17 @@ int ff_hevc_decode_nal_vps(GetBitContext *gb, AVCodecContext *avctx,
>> goto err;
>> }
>> for (i = 0; i < vps->vps_num_hrd_parameters; i++) {
>> + HEVCHdrParams *hdr = ff_refstruct_allocz(sizeof(*hdr));
>> int common_inf_present = 1;
>>
>> + if (!hdr)
>> + return AVERROR(ENOMEM);
>> +
>> get_ue_golomb_long(gb); // hrd_layer_set_idx
>> if (i)
>> common_inf_present = get_bits1(gb);
>> - decode_hrd(gb, common_inf_present, &vps->hdr[i],
>> +
>> + decode_hrd(gb, common_inf_present, hdr,
>> vps->vps_max_sub_layers);
>> }
>
> Why do you allocate the HEVCHdrParams separately when you know
> vps_num_hrd_parameters before allocating the first one?
You want me to allocate all of them with a single ff_refstruct_allocz()
and store individual pointers for each?
>
>> }
>> diff --git a/libavcodec/hevc_ps.h b/libavcodec/hevc_ps.h
>> index 9cdec9b6c1..ff94f90a5e 100644
>> --- a/libavcodec/hevc_ps.h
>> +++ b/libavcodec/hevc_ps.h
>> @@ -150,7 +150,7 @@ typedef struct PTL {
>>
>> typedef struct HEVCVPS {
>> unsigned int vps_id;
>> - HEVCHdrParams hdr[HEVC_MAX_LAYER_SETS];
>> + HEVCHdrParams *hdr[HEVC_MAX_LAYER_SETS];
>>
>> uint8_t vps_temporal_id_nesting_flag : 1;
>> uint8_t vps_sub_layer_ordering_info_present_flag : 1;
>> diff --git a/libavcodec/vulkan_hevc.c b/libavcodec/vulkan_hevc.c
>> index 239bff75e5..a89d09a372 100644
>> --- a/libavcodec/vulkan_hevc.c
>> +++ b/libavcodec/vulkan_hevc.c
>> @@ -563,7 +563,7 @@ static void set_vps(const HEVCVPS *vps,
>> HEVCHeaderVPSSet sls[])
>> {
>> for (int i = 0; i < vps->vps_num_hrd_parameters; i++) {
>> - const HEVCHdrParams *src = &vps->hdr[i];
>> + const HEVCHdrParams *src = vps->hdr[i];
>>
>> sls_hdr[i] = (StdVideoH265HrdParameters) {
>> .flags = (StdVideoH265HrdFlags) {
>
> _______________________________________________
> 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".
_______________________________________________
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".
next prev parent reply other threads:[~2024-03-21 12:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 23:35 James Almer
2024-03-21 4:00 ` Michael Niedermayer
2024-03-21 11:15 ` Andreas Rheinhardt
2024-03-21 12:11 ` James Almer [this message]
2024-03-21 12:19 ` Andreas Rheinhardt
2024-03-21 12:29 ` James Almer
2024-03-21 12:54 ` Andreas Rheinhardt
2024-03-27 7:41 ` Wu, Tong1
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=78d1ee1d-9617-4757-833d-12719831862d@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