BPF List
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: Alan Maguire <alan.maguire@oracle.com>, Jiri Olsa <olsajiri@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
	Alexei Starovoitov <ast@kernel.org>,
	bpf@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	dwarves@vger.kernel.org
Subject: Re: [PATCH] fix linux kernel BTF builds: increase max percpu variables by 10x
Date: Thu, 29 Feb 2024 10:15:23 -0800	[thread overview]
Message-ID: <f248cf92-038c-480f-b077-f7d56ebc55bc@nvidia.com> (raw)
In-Reply-To: <34157878-c480-44bb-91d6-9024da329998@oracle.com>

> ...
> Running
> 
> bpftool btf dump file vmlinux |grep "] VAR"
> 

$ bpftool btf dump file vmlinux |grep "] VAR" | wc -l
4852

$ bpftool btf dump file vmlinux |grep "] VAR" | tail -5
[136994] VAR '_alloc_tag_cntr.9' type_id=703, linkage=static
[137003] VAR '_alloc_tag_cntr.5' type_id=703, linkage=static
[137004] VAR '_alloc_tag_cntr.7' type_id=703, linkage=static
[137005] VAR '_alloc_tag_cntr.17' type_id=703, linkage=static
[137018] VAR '_alloc_tag_cntr.14' type_id=703, linkage=static

> ...should give us a sense of what's going on. I only see 375 per-cpu
> variables when I do this so maybe there's something
> kernel-config-specific that might explain why you have so many more?

Yes, as mentioned earlier, this is specifically due to the .config.
The .config is a huge distro configuration that has a lot of modules
enabled.


thanks,
-- 
John Hubbard
NVIDIA


  reply	other threads:[~2024-02-29 18:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-28  3:21 [PATCH] fix linux kernel BTF builds: increase max percpu variables by 10x John Hubbard
2024-02-28  9:20 ` Jiri Olsa
2024-02-28 12:04   ` Alan Maguire
2024-02-28 23:21     ` John Hubbard
2024-02-29  9:17       ` Alan Maguire
2024-02-29 18:15         ` John Hubbard [this message]
2024-03-01 14:14           ` Jiri Olsa
2024-03-01 18:32             ` John Hubbard
2024-03-01 19:15               ` Suren Baghdasaryan

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=f248cf92-038c-480f-b077-f7d56ebc55bc@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=acme@redhat.com \
    --cc=alan.maguire@oracle.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=dwarves@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olsajiri@gmail.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