From: Yonghong Song <yonghong.song@linux.dev>
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>, bpf@vger.kernel.org
Cc: Yonghong Song <yhs@meta.com>,
Eduard Zingerman <eddyz87@gmail.com>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
david.faust@oracle.com, cupertino.miranda@oracle.com
Subject: Re: [PATCH bpf-next V2] bpf: abstract loop unrolling pragmas in BPF selftests
Date: Thu, 8 Feb 2024 14:12:06 -0800 [thread overview]
Message-ID: <cff448e3-f751-482d-ae4d-65a2bca82b20@linux.dev> (raw)
In-Reply-To: <20240208203612.29611-1-jose.marchesi@oracle.com>
On 2/8/24 12:36 PM, Jose E. Marchesi wrote:
> [Changes from V1:
> - Avoid conflict by rebasing with latest master.]
>
> Some BPF tests use loop unrolling compiler pragmas that are clang
> specific and not supported by GCC. These pragmas, along with their
> GCC equivalences are:
>
> #pragma clang loop unroll_count(N)
> #pragma GCC unroll N
>
> #pragma clang loop unroll(full)
> #pragma GCC unroll 65534
>
> #pragma clang loop unroll(disable)
> #pragma GCC unroll 1
>
> #pragma unroll [aka #pragma clang loop unroll(enable)]
> There is no GCC equivalence to this pragma. It enables unrolling on
> loops that the compiler would not ordinarily unroll even with
> -O2|-funroll-loops, but it is not equivalent to full unrolling
> either.
>
> This patch adds a new header progs/bpf_compiler.h that defines the
> following macros, which correspond to each pair of compiler-specific
> pragmas above:
>
> __pragma_loop_unroll_count(N)
> __pragma_loop_unroll_full
> __pragma_loop_no_unroll
> __pragma_loop_unroll
>
> The selftests using loop unrolling pragmas are then changed to include
> the header and use these macros in place of the explicit pragmas.
>
> Tested in bpf-next master.
> No regressions.
>
> Signed-off-by: Jose E. Marchesi <jose.marchesi@oracle.com>
> Cc: Yonghong Song <yhs@meta.com>
> Cc: Eduard Zingerman <eddyz87@gmail.com>
> Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>
> Cc: david.faust@oracle.com
> Cc: cupertino.miranda@oracle.com
Acked-by: Yonghong Song <yonghong.song@linux.dev>
next prev parent reply other threads:[~2024-02-08 22:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 20:36 [PATCH bpf-next V2] bpf: abstract loop unrolling pragmas in BPF selftests Jose E. Marchesi
2024-02-08 22:12 ` Yonghong Song [this message]
2024-02-13 19:30 ` 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=cff448e3-f751-482d-ae4d-65a2bca82b20@linux.dev \
--to=yonghong.song@linux.dev \
--cc=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=cupertino.miranda@oracle.com \
--cc=david.faust@oracle.com \
--cc=eddyz87@gmail.com \
--cc=jose.marchesi@oracle.com \
--cc=yhs@meta.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