From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: <netdev@vger.kernel.org>,
Anthony Nguyen <anthony.l.nguyen@intel.com>,
Jakub Kicinski <kuba@kernel.org>,
Kees Cook <keescook@chromium.org>
Cc: Jacob Keller <jacob.e.keller@intel.com>,
<intel-wired-lan@lists.osuosl.org>,
Alexander Lobakin <aleksander.lobakin@intel.com>,
<linux-hardening@vger.kernel.org>,
Steven Zou <steven.zou@intel.com>,
David Laight <David.Laight@ACULAB.COM>
Subject: Re: [RFC net-next v4 0/7] introduce DEFINE_FLEX() macro
Date: Mon, 4 Sep 2023 14:37:53 +0200 [thread overview]
Message-ID: <1cc1db76-3e3f-3cc6-1c76-9e01cccd0ae5@intel.com> (raw)
In-Reply-To: <20230904123107.116381-1-przemyslaw.kitszel@intel.com>
On 9/4/23 14:31, Przemek Kitszel wrote:
> Add DEFINE_FLEX() macro, that helps on-stack allocation of structures
> with trailing flex array member.
> Expose __struct_size() macro which reads size of data allocated
> by DEFINE_FLEX().
>
> Accompany new macros introduction with actual usage,
> in the ice driver - hence targeting for netdev tree
> - please me know if it is best approach here?
I have put this question in each revision up to now,
but perhaps no one noticed it, so making it stand out.
>
> Obvious benefits include simpler resulting code, less heap usage,
> less error checking. Less obvious is the fact that compiler has
> more room to optimize, and as a whole, even with more stuff on the stack,
> we end up with overall better (smaller) report from bloat-o-meter:
> add/remove: 8/6 grow/shrink: 7/18 up/down: 2211/-2270 (-59)
> (individual results in each patch).
>
> v4: _Static_assert() to ensure compiletime const count param
> v3: tidy up 1st patch
> v2: Kees: reusing __struct_size() instead of doubling it as a new macro
>
> Przemek Kitszel (7):
> overflow: add DEFINE_FLEX() for on-stack allocs
> ice: ice_sched_remove_elems: replace 1 elem array param by u32
> ice: drop two params of ice_aq_move_sched_elems()
> ice: make use of DEFINE_FLEX() in ice_ddp.c
> ice: make use of DEFINE_FLEX() for struct ice_aqc_add_tx_qgrp
> ice: make use of DEFINE_FLEX() for struct ice_aqc_dis_txq_item
> ice: make use of DEFINE_FLEX() in ice_switch.c
>
> drivers/net/ethernet/intel/ice/ice_common.c | 20 ++-----
> drivers/net/ethernet/intel/ice/ice_ddp.c | 39 ++++---------
> drivers/net/ethernet/intel/ice/ice_lag.c | 48 ++++------------
> drivers/net/ethernet/intel/ice/ice_lib.c | 23 ++------
> drivers/net/ethernet/intel/ice/ice_sched.c | 56 ++++++------------
> drivers/net/ethernet/intel/ice/ice_sched.h | 6 +-
> drivers/net/ethernet/intel/ice/ice_switch.c | 63 +++++----------------
> drivers/net/ethernet/intel/ice/ice_xsk.c | 22 +++----
> include/linux/compiler_types.h | 32 +++++++----
> include/linux/fortify-string.h | 4 --
> include/linux/overflow.h | 35 ++++++++++++
> 11 files changed, 130 insertions(+), 218 deletions(-)
>
>
> base-commit: bd6c11bc43c496cddfc6cf603b5d45365606dbd5
next prev parent reply other threads:[~2023-09-04 12:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 12:31 [RFC net-next v4 0/7] introduce DEFINE_FLEX() macro Przemek Kitszel
2023-09-04 12:31 ` [RFC net-next v4 1/7] overflow: add DEFINE_FLEX() for on-stack allocs Przemek Kitszel
2023-09-05 3:55 ` Kees Cook
2023-09-04 12:31 ` [RFC net-next v4 2/7] ice: ice_sched_remove_elems: replace 1 elem array param by u32 Przemek Kitszel
2023-09-04 12:31 ` [RFC net-next v4 3/7] ice: drop two params of ice_aq_move_sched_elems() Przemek Kitszel
2023-09-04 12:31 ` [RFC net-next v4 4/7] ice: make use of DEFINE_FLEX() in ice_ddp.c Przemek Kitszel
2023-09-04 12:31 ` [RFC net-next v4 5/7] ice: make use of DEFINE_FLEX() for struct ice_aqc_add_tx_qgrp Przemek Kitszel
2023-09-04 12:31 ` [RFC net-next v4 6/7] ice: make use of DEFINE_FLEX() for struct ice_aqc_dis_txq_item Przemek Kitszel
2023-09-04 12:31 ` [RFC net-next v4 7/7] ice: make use of DEFINE_FLEX() in ice_switch.c Przemek Kitszel
2023-09-04 12:37 ` Przemek Kitszel [this message]
2023-09-05 3:53 ` [RFC net-next v4 0/7] introduce DEFINE_FLEX() macro Kees Cook
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=1cc1db76-3e3f-3cc6-1c76-9e01cccd0ae5@intel.com \
--to=przemyslaw.kitszel@intel.com \
--cc=David.Laight@ACULAB.COM \
--cc=aleksander.lobakin@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steven.zou@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