Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <simon.horman@corigine.com>
To: Alexander Lobakin <aleksander.lobakin@intel.com>
Cc: jiri@resnulli.us, netdev@vger.kernel.org, idosch@nvidia.com,
	jesse.brandeburg@intel.com, kuba@kernel.org,
	intel-wired-lan@lists.osuosl.org, pabeni@redhat.com,
	davem@davemloft.net
Subject: Re: [Intel-wired-lan] [RFC PATCH iwl-next 2/6] ip_tunnel: convert __be16 tunnel flags to bitmaps
Date: Tue, 6 Jun 2023 17:25:18 +0200	[thread overview]
Message-ID: <ZH9P3hXDcEIWzGqQ@corigine.com> (raw)
In-Reply-To: <63ccadd7-316d-cb1f-b1d6-4f2911120959@intel.com>

On Tue, Jun 06, 2023 at 03:17:47PM +0200, Alexander Lobakin wrote:
> From: Simon Horman <simon.horman@corigine.com>
> Date: Mon, 5 Jun 2023 11:23:34 +0200
> 
> > On Thu, Jun 01, 2023 at 03:19:25PM +0200, Marcin Szycik wrote:
> >> From: Alexander Lobakin <alexandr.lobakin@intel.com>
> 
> [...]
> 
> >>  net/ipv4/fou_bpf.c                            |   2 +-
> >>  net/ipv4/gre_demux.c                          |   2 +-
> >>  net/ipv4/ip_gre.c                             | 131 +++++++++++-------
> >>  net/ipv4/ip_tunnel.c                          |  51 ++++---
> >>  net/ipv4/ip_tunnel_core.c                     |  81 +++++++----
> >>  net/ipv4/ip_vti.c                             |  31 +++--
> >>  net/ipv4/ipip.c                               |  21 ++-
> >>  net/ipv4/udp_tunnel_core.c                    |   5 +-
> >>  net/ipv6/ip6_gre.c                            |  87 +++++++-----
> >>  net/ipv6/ip6_tunnel.c                         |  14 +-
> >>  net/ipv6/sit.c                                |   9 +-
> >>  net/netfilter/ipvs/ip_vs_core.c               |   6 +-
> >>  net/netfilter/ipvs/ip_vs_xmit.c               |  20 +--
> >>  net/netfilter/nft_tunnel.c                    |  45 +++---
> >>  net/openvswitch/flow_netlink.c                |  55 ++++----
> >>  net/psample/psample.c                         |  26 ++--
> >>  net/sched/act_tunnel_key.c                    |  39 +++---
> >>  net/sched/cls_flower.c                        |  27 ++--
> >>  40 files changed, 695 insertions(+), 392 deletions(-)
> > 
> > nit: this is a rather long patch
> I know, but you can't do anything with it. I'm changing the type of the
> fields from `__be16` to `unsigned long *` and they're accessed in a good
> ton of places around the kernel. This patch is atomic despite being
> huge, any separation would break compilation ¯\_(ツ)_/¯

Yes, I concede that it may well be the least worst option.
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

  reply	other threads:[~2023-06-06 15:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-01 13:19 [Intel-wired-lan] [RFC PATCH iwl-next 0/6] ice: Add PFCP filter support Marcin Szycik
2023-06-01 13:19 ` [Intel-wired-lan] [RFC PATCH iwl-next 1/6] ip_tunnel: use a separate struct to store tunnel params in the kernel Marcin Szycik
2023-06-05  9:23   ` Simon Horman
2023-06-01 13:19 ` [Intel-wired-lan] [RFC PATCH iwl-next 2/6] ip_tunnel: convert __be16 tunnel flags to bitmaps Marcin Szycik
2023-06-02 13:19   ` Alexander Lobakin
2023-06-05  9:23   ` Simon Horman
2023-06-05 14:21     ` Marcin Szycik
2023-06-06 13:17     ` Alexander Lobakin
2023-06-06 15:25       ` Simon Horman [this message]
2023-06-01 13:19 ` [Intel-wired-lan] [RFC PATCH iwl-next 3/6] pfcp: add PFCP module Marcin Szycik
2023-06-05  9:26   ` Simon Horman
2023-06-01 13:19 ` [Intel-wired-lan] [RFC PATCH iwl-next 4/6] pfcp: always set pfcp metadata Marcin Szycik
2023-06-05  9:34   ` Simon Horman
2023-06-01 13:19 ` [Intel-wired-lan] [RFC PATCH iwl-next 5/6] ice: refactor ICE_TC_FLWR_FIELD_ENC_OPTS Marcin Szycik
2023-06-05  9:36   ` Simon Horman
2023-06-01 13:19 ` [Intel-wired-lan] [RFC PATCH iwl-next 6/6] ice: Add support for PFCP hardware offload in switchdev Marcin Szycik
2023-06-05  9:38   ` Simon Horman

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=ZH9P3hXDcEIWzGqQ@corigine.com \
    --to=simon.horman@corigine.com \
    --cc=aleksander.lobakin@intel.com \
    --cc=davem@davemloft.net \
    --cc=idosch@nvidia.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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