From: Steven Rostedt <rostedt@goodmis.org>
To: Menglong Dong <menglong8.dong@gmail.com>
Cc: peterz@infradead.org, mark.rutland@arm.com,
alexei.starovoitov@gmail.com, catalin.marinas@arm.com,
will@kernel.org, mhiramat@kernel.org, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
x86@kernel.org, hpa@zytor.com, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, martin.lau@linux.dev,
eddyz87@gmail.com, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
jolsa@kernel.org, davem@davemloft.net, dsahern@kernel.org,
mathieu.desnoyers@efficios.com, nathan@kernel.org,
nick.desaulniers+lkml@gmail.com, morbo@google.com,
samitolvanen@google.com, kees@kernel.org,
dongml2@chinatelecom.cn, akpm@linux-foundation.org,
riel@surriel.com, rppt@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
bpf@vger.kernel.org, netdev@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH bpf-next v3 3/4] x86: implement per-function metadata storage for x86
Date: Mon, 3 Mar 2025 11:05:59 -0500 [thread overview]
Message-ID: <20250303110559.5a584602@gandalf.local.home> (raw)
In-Reply-To: <20250303065345.229298-4-dongml2@chinatelecom.cn>
On Mon, 3 Mar 2025 14:53:44 +0800
Menglong Dong <menglong8.dong@gmail.com> wrote:
> In the third case, we make the kernel function 32 bytes aligned, and there
> will be 32 bytes padding before the functions. According to my testing,
> the text size didn't increase on this case, which is weird.
>
> With 16-bytes padding:
>
> -rwxr-xr-x 1 401190688 x86-dev/vmlinux*
> -rw-r--r-- 1 251068 x86-dev/vmlinux.a
> -rw-r--r-- 1 851892992 x86-dev/vmlinux.o
> -rw-r--r-- 1 12395008 x86-dev/arch/x86/boot/bzImage
>
> With 32-bytes padding:
>
> -rwxr-xr-x 1 401318128 x86-dev/vmlinux*
> -rw-r--r-- 1 251154 x86-dev/vmlinux.a
> -rw-r--r-- 1 853636704 x86-dev/vmlinux.o
> -rw-r--r-- 1 12509696 x86-dev/arch/x86/boot/bzImage
Use the "size" command to see the differences in sizes and not the file size.
$ size vmlinux
text data bss dec hex filename
36892658 9798658 16982016 63673332 3cb93f4 vmlinux
-- Steve
next prev parent reply other threads:[~2025-03-03 16:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 6:53 [PATCH bpf-next v3 0/4] per-function storage support Menglong Dong
2025-03-03 6:53 ` [PATCH bpf-next v3 1/4] x86/ibt: factor out cfi and fineibt offset Menglong Dong
2025-03-03 9:18 ` Peter Zijlstra
2025-03-03 10:51 ` Menglong Dong
2025-03-03 11:24 ` Peter Zijlstra
2025-03-03 6:53 ` [PATCH bpf-next v3 2/4] add per-function metadata storage support Menglong Dong
2025-03-03 6:53 ` [PATCH bpf-next v3 3/4] x86: implement per-function metadata storage for x86 Menglong Dong
2025-03-03 16:05 ` Steven Rostedt [this message]
2025-03-04 2:07 ` Menglong Dong
2025-03-04 3:06 ` Menglong Dong
2025-03-03 6:53 ` [PATCH bpf-next v3 4/4] arm64: implement per-function metadata storage for arm64 Menglong Dong
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=20250303110559.5a584602@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bp@alien8.de \
--cc=bpf@vger.kernel.org \
--cc=catalin.marinas@arm.com \
--cc=daniel@iogearbox.net \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=dongml2@chinatelecom.cn \
--cc=dsahern@kernel.org \
--cc=eddyz87@gmail.com \
--cc=hpa@zytor.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kees@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mark.rutland@arm.com \
--cc=martin.lau@linux.dev \
--cc=mathieu.desnoyers@efficios.com \
--cc=menglong8.dong@gmail.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=rppt@kernel.org \
--cc=samitolvanen@google.com \
--cc=sdf@fomichev.me \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=yonghong.song@linux.dev \
/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