From: "Jose E. Marchesi" <jose.marchesi@oracle.com>
To: Yonghong Song <yonghong.song@linux.dev>
Cc: bpf@vger.kernel.org,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
david.faust@oracle.com, cupertino.miranda@oracle.com
Subject: Re: [PATCH bpf-next] bpf: fix bpf_ksym_exists in GCC
Date: Thu, 02 May 2024 20:23:58 +0200 [thread overview]
Message-ID: <874jbgqdhd.fsf@oracle.com> (raw)
In-Reply-To: <c4d99195-f000-47f2-b167-12e76b705dc9@linux.dev> (Yonghong Song's message of "Mon, 29 Apr 2024 13:52:48 -0700")
> .long runqueues
> .long 3264
> .long 388
Just to be sure, there seems to be a little discrepancy. The size of
runqueues (struct rq) in the latest bpf-next is 3456 instead of 3264,
when compiled by both clang 18 and GCC. This is correctly reflected in
the BTF generated by both compilers.
Is the size of struct rq different in your testing machine?
next prev parent reply other threads:[~2024-05-02 18:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-28 11:25 [PATCH bpf-next] bpf: fix bpf_ksym_exists in GCC Jose E. Marchesi
2024-04-29 20:52 ` Yonghong Song
2024-05-02 17:44 ` Jose E. Marchesi
2024-05-03 4:56 ` Yonghong Song
2024-05-02 18:23 ` Jose E. Marchesi [this message]
2024-05-03 4:58 ` Yonghong Song
2024-05-03 5:52 ` Andrii Nakryiko
2024-05-03 7:50 ` Jose E. Marchesi
2024-05-03 6:00 ` patchwork-bot+netdevbpf
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=874jbgqdhd.fsf@oracle.com \
--to=jose.marchesi@oracle.com \
--cc=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=cupertino.miranda@oracle.com \
--cc=david.faust@oracle.com \
--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