From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: Marcin Szycik <marcin.szycik@linux.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, simon.horman@corigine.com,
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: Fri, 2 Jun 2023 15:19:52 +0200 [thread overview]
Message-ID: <bd58b5a8-de29-d80c-9440-4809162951db@intel.com> (raw)
In-Reply-To: <20230601131929.294667-3-marcin.szycik@linux.intel.com>
From: Marcin Szycik <marcin.szycik@linux.intel.com>
Date: Thu, 1 Jun 2023 15:19:25 +0200
> From: Alexander Lobakin <alexandr.lobakin@intel.com>
>
> Historically, tunnel flags like TUNNEL_CSUM or TUNNEL_ERSPAN_OPT
> have been defined as __be16. Now all of those 16 bits are occupied
> and there's no more free space for new flags.
> It can't be simply switched to a bigger container with no
> adjustments to the values, since it's an explicit Endian storage,
> and on LE systems (__be16)0x0001 equals to
> (__be64)0x0001000000000000.
[...]
Little comment on this: yes, I'm planning to extend UAPI to be able to
use more bits, but using Netlink bigint, which I posted last autumn,
then switched to another project, now I'm a little (a ton) busy with
urgent another one... Hopefully I'll send v3 in 2 weeks or so.
PFCP doesn't depend on it anyway, so this can be done separately.
Thanks,
Olek
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2023-06-02 13:21 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 [this message]
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
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=bd58b5a8-de29-d80c-9440-4809162951db@intel.com \
--to=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=marcin.szycik@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=simon.horman@corigine.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