[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 10 Oct 2019 03:43:14 +0000
From: Alexei Starovoitov <ast@...com>
To: Martin Lau <kafai@...com>, Alexei Starovoitov <ast@...nel.org>
CC: "davem@...emloft.net" <davem@...emloft.net>,
"daniel@...earbox.net" <daniel@...earbox.net>,
"x86@...nel.org" <x86@...nel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"bpf@...r.kernel.org" <bpf@...r.kernel.org>,
Kernel Team <Kernel-team@...com>
Subject: Re: [PATCH bpf-next 03/10] bpf: process in-kernel BTF
On 10/9/19 1:51 PM, Martin Lau wrote:
>> err = btf_check_all_metas(env);
>> + if (err)
>> + goto errout;
>> +
> Considering btf_vmlinux is already safe, any concern in making an extra
> call to btf_check_all_types()?
Only concern is additional memory resolved_* arrays will take.
The usual cpu vs memory trade off.
For this set I think extra while loop to skip btf modifiers
is better than extra array.
Yours could be different. And that's ok.
Powered by blists - more mailing lists