public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tianchen Ding <dtcccc@linux.alibaba.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Tejun Heo <tj@kernel.org>,
	David Vernet <void@manifault.com>,
	Peter Zijlstra <peterz@infradead.org>, bpf <bpf@vger.kernel.org>
Subject: Re: [PATCH] sched_ext: Use BTF_ID to resolve task_struct
Date: Thu, 17 Oct 2024 09:57:17 +0800	[thread overview]
Message-ID: <fa9600d8-2a6c-4c74-8e42-31d669c06b59@linux.alibaba.com> (raw)
In-Reply-To: <CAADnVQ+gL48HGcs0JyLfq17D-qXyeZEoBJwGgGTO1JcJ3Ykqtw@mail.gmail.com>

On 2024/10/17 00:57, Alexei Starovoitov wrote:
> On Tue, Oct 15, 2024 at 7:42 PM Tianchen Ding <dtcccc@linux.alibaba.com> wrote:
>>
>> Save the searching time during bpf_scx_init.
>>
>> Signed-off-by: Tianchen Ding <dtcccc@linux.alibaba.com>
>> ---
>>   kernel/sched/ext.c | 12 +++---------
>>   1 file changed, 3 insertions(+), 9 deletions(-)
>>
>> diff --git a/kernel/sched/ext.c b/kernel/sched/ext.c
>> index 609b9fb00d6f..1d11a96eefb8 100644
>> --- a/kernel/sched/ext.c
>> +++ b/kernel/sched/ext.c
>> @@ -5343,7 +5343,7 @@ static int scx_ops_enable(struct sched_ext_ops *ops, struct bpf_link *link)
>>
>>   extern struct btf *btf_vmlinux;
>>   static const struct btf_type *task_struct_type;
>> -static u32 task_struct_type_id;
>> +BTF_ID_LIST_SINGLE(task_struct_btf_ids, struct, task_struct);
>>
>>   static bool set_arg_maybe_null(const char *op, int arg_n, int off, int size,
>>                                 enum bpf_access_type type,
>> @@ -5395,7 +5395,7 @@ static bool set_arg_maybe_null(const char *op, int arg_n, int off, int size,
>>                   */
>>                  info->reg_type = PTR_MAYBE_NULL | PTR_TO_BTF_ID | PTR_TRUSTED;
>>                  info->btf = btf_vmlinux;
>> -               info->btf_id = task_struct_type_id;
>> +               info->btf_id = task_struct_btf_ids[0];
>>
>>                  return true;
>>          }
>> @@ -5547,13 +5547,7 @@ static void bpf_scx_unreg(void *kdata, struct bpf_link *link)
>>
>>   static int bpf_scx_init(struct btf *btf)
>>   {
>> -       s32 type_id;
>> -
>> -       type_id = btf_find_by_name_kind(btf, "task_struct", BTF_KIND_STRUCT);
>> -       if (type_id < 0)
>> -               return -EINVAL;
>> -       task_struct_type = btf_type_by_id(btf, type_id);
>> -       task_struct_type_id = type_id;
>> +       task_struct_type = btf_type_by_id(btf, task_struct_btf_ids[0]);
> 
> Good optimization, but it's also unnecessary.
> 
> btf_id is already in btf_tracing_ids[BTF_TRACING_TYPE_TASK].

Get it. Thanks!

BTW, do you think we should add a zero check for 
btf_tracing_ids[BTF_TRACING_TYPE_TASK] here?
task_struct should always be valid. If something wrong, resolve_btfids will also 
throw a warning. I'm not sure whether to add a sanity check here.

  reply	other threads:[~2024-10-17  1:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-16  2:41 [PATCH] sched_ext: Use BTF_ID to resolve task_struct Tianchen Ding
2024-10-16 16:57 ` Alexei Starovoitov
2024-10-17  1:57   ` Tianchen Ding [this message]
2024-10-17  2:12     ` Alexei Starovoitov

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=fa9600d8-2a6c-4c74-8e42-31d669c06b59@linux.alibaba.com \
    --to=dtcccc@linux.alibaba.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=tj@kernel.org \
    --cc=void@manifault.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