From: Jakub Kicinski <kuba@kernel.org>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, pabeni@redhat.com, edumazet@google.com,
netdev@vger.kernel.org,
Alexander Lobakin <aleksander.lobakin@intel.com>,
przemyslaw.kitszel@intel.com, joshua.a.hay@intel.com,
michal.kubiak@intel.com,
nex.sw.ncis.osdt.itp.upstreaming@intel.com,
"Jose E . Marchesi" <jose.marchesi@oracle.com>
Subject: Re: [PATCH net-next v2 1/9] unroll: add generic loop unroll helpers
Date: Tue, 20 Aug 2024 17:55:39 -0700 [thread overview]
Message-ID: <20240820175539.6b1cec2b@kernel.org> (raw)
In-Reply-To: <20240819223442.48013-2-anthony.l.nguyen@intel.com>
On Mon, 19 Aug 2024 15:34:33 -0700 Tony Nguyen wrote:
> There are cases when we need to explicitly unroll loops. For example,
> cache operations, filling DMA descriptors on very high speeds etc.
> Add compiler-specific attribute macros to give the compiler a hint
> that we'd like to unroll a loop.
> Example usage:
>
> #define UNROLL_BATCH 8
>
> unrolled_count(UNROLL_BATCH)
> for (u32 i = 0; i < UNROLL_BATCH; i++)
> op(priv, i);
>
> Note that sometimes the compilers won't unroll loops if they think this
> would have worse optimization and perf than without unrolling, and that
> unroll attributes are available only starting GCC 8. For older compiler
> versions, no hints/attributes will be applied.
> For better unrolling/parallelization, don't have any variables that
> interfere between iterations except for the iterator itself.
Please run the submissions thru get_maintainers
next prev parent reply other threads:[~2024-08-21 0:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 22:34 [PATCH net-next v2 0/9][pull request] idpf: XDP chapter II: convert Tx completion to libeth Tony Nguyen
2024-08-19 22:34 ` [PATCH net-next v2 1/9] unroll: add generic loop unroll helpers Tony Nguyen
2024-08-21 0:55 ` Jakub Kicinski [this message]
2024-08-22 15:15 ` Alexander Lobakin
2024-08-22 22:59 ` Jakub Kicinski
2024-08-22 23:35 ` Tony Nguyen
2024-08-23 12:37 ` Alexander Lobakin
2024-08-19 22:34 ` [PATCH net-next v2 2/9] libeth: add common queue stats Tony Nguyen
2024-08-21 1:17 ` Jakub Kicinski
2024-08-22 15:13 ` Alexander Lobakin
2024-08-22 23:17 ` Jakub Kicinski
2024-08-23 12:59 ` Alexander Lobakin
2024-08-27 1:09 ` Jakub Kicinski
2024-08-27 15:31 ` Alexander Lobakin
2024-08-27 18:29 ` Jakub Kicinski
2024-08-28 15:06 ` Alexander Lobakin
2024-08-28 20:22 ` Jakub Kicinski
2024-08-29 12:01 ` Alexander Lobakin
2024-08-29 14:39 ` Jakub Kicinski
2024-08-19 22:34 ` [PATCH net-next v2 3/9] libie: add Tx buffer completion helpers Tony Nguyen
2024-08-19 22:34 ` [PATCH net-next v2 4/9] idpf: convert to libie Tx buffer completion Tony Nguyen
2024-08-19 22:34 ` [PATCH net-next v2 5/9] netdevice: add netdev_tx_reset_subqueue() shorthand Tony Nguyen
2024-08-19 22:34 ` [PATCH net-next v2 6/9] idpf: refactor Tx completion routines Tony Nguyen
2024-08-19 22:34 ` [PATCH net-next v2 7/9] idpf: fix netdev Tx queue stop/wake Tony Nguyen
2024-08-19 22:34 ` [PATCH net-next v2 8/9] idpf: enable WB_ON_ITR Tony Nguyen
2024-08-19 22:34 ` [PATCH net-next v2 9/9] idpf: switch to libeth generic statistics Tony Nguyen
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=20240820175539.6b1cec2b@kernel.org \
--to=kuba@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jose.marchesi@oracle.com \
--cc=joshua.a.hay@intel.com \
--cc=michal.kubiak@intel.com \
--cc=netdev@vger.kernel.org \
--cc=nex.sw.ncis.osdt.itp.upstreaming@intel.com \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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;
as well as URLs for NNTP newsgroup(s).