From: Jiri Pirko <jiri@resnulli.us>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, davem@davemloft.net,
edumazet@google.com, leon@kernel.org, saeedm@nvidia.com,
moshe@nvidia.com, jesse.brandeburg@intel.com,
anthony.l.nguyen@intel.com, tariqt@nvidia.com, idosch@nvidia.com,
petrm@nvidia.com, simon.horman@corigine.com,
ecree.xilinx@gmail.com, habetsm.xilinx@gmail.com,
michal.wilczynski@intel.com, jacob.e.keller@intel.com
Subject: Re: [patch net-next 01/15] devlink: introduce port ops placeholder
Date: Thu, 25 May 2023 08:07:08 +0200 [thread overview]
Message-ID: <ZG77DAskJxpDYbdi@nanopsycho> (raw)
In-Reply-To: <20230524214811.0fb25930@kernel.org>
Thu, May 25, 2023 at 06:48:11AM CEST, kuba@kernel.org wrote:
>On Wed, 24 May 2023 14:18:22 +0200 Jiri Pirko wrote:
>> @@ -6799,6 +6799,7 @@ EXPORT_SYMBOL_GPL(devlink_port_fini);
>> * @devlink: devlink
>> * @devlink_port: devlink port
>> * @port_index: driver-specific numerical identifier of the port
>> + * @ops: port ops
>> *
>> * Register devlink port with provided port index. User can use
>> * any indexing, even hw-related one. devlink_port structure
>> @@ -6806,9 +6807,10 @@ EXPORT_SYMBOL_GPL(devlink_port_fini);
>> * Note that the caller should take care of zeroing the devlink_port
>> * structure.
>> */
>> -int devl_port_register(struct devlink *devlink,
>> - struct devlink_port *devlink_port,
>> - unsigned int port_index)
>> +int devl_port_register_with_ops(struct devlink *devlink,
>> + struct devlink_port *devlink_port,
>> + unsigned int port_index,
>> + const struct devlink_port_ops *ops)
>> {
>> int err;
>
>function name in kdoc needs an update
Ah, will fix.
>
>> @@ -6819,6 +6821,7 @@ int devl_port_register(struct devlink *devlink,
>> devlink_port_init(devlink, devlink_port);
>> devlink_port->registered = true;
>> devlink_port->index = port_index;
>> + devlink_port->ops = ops;
>> spin_lock_init(&devlink_port->type_lock);
>> INIT_LIST_HEAD(&devlink_port->reporter_list);
>> err = xa_insert(&devlink->ports, port_index, devlink_port, GFP_KERNEL);
>> @@ -6830,7 +6833,7 @@ int devl_port_register(struct devlink *devlink,
>> devlink_port_notify(devlink_port, DEVLINK_CMD_PORT_NEW);
>> return 0;
>> }
>> -EXPORT_SYMBOL_GPL(devl_port_register);
>> +EXPORT_SYMBOL_GPL(devl_port_register_with_ops);
>>
>> /**
>> * devlink_port_register - Register devlink port
>> @@ -6838,6 +6841,7 @@ EXPORT_SYMBOL_GPL(devl_port_register);
>> * @devlink: devlink
>> * @devlink_port: devlink port
>> * @port_index: driver-specific numerical identifier of the port
>> + * @ops: port ops
>> *
>> * Register devlink port with provided port index. User can use
>> * any indexing, even hw-related one. devlink_port structure
>> @@ -6847,18 +6851,20 @@ EXPORT_SYMBOL_GPL(devl_port_register);
>> *
>> * Context: Takes and release devlink->lock <mutex>.
>> */
>> -int devlink_port_register(struct devlink *devlink,
>> - struct devlink_port *devlink_port,
>> - unsigned int port_index)
>> +int devlink_port_register_with_ops(struct devlink *devlink,
>> + struct devlink_port *devlink_port,
>> + unsigned int port_index,
>> + const struct devlink_port_ops *ops)
>
>same here.
Yeah, will fix.
>
>BTW do we need to provide the "devlink_*" form of this API or can we
>use this as an opportunity to move everyone to devl_*. Even if the
>driver just wraps the call with devl_lock(), sooner or later people
>will coalesce the locking in the drivers, I hope.
It is on my list, stay tuned, will address in a follow-up.
>--
>pw-bot: cr
next prev parent reply other threads:[~2023-05-25 6:07 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 12:18 [patch net-next 00/15] devlink: move port ops into separate structure Jiri Pirko
2023-05-24 12:18 ` [patch net-next 01/15] devlink: introduce port ops placeholder Jiri Pirko
2023-05-25 4:48 ` Jakub Kicinski
2023-05-25 6:07 ` Jiri Pirko [this message]
2023-05-24 12:18 ` [patch net-next 02/15] ice: register devlink port for PF with ops Jiri Pirko
2023-05-24 17:30 ` Jesse Brandeburg
2023-05-24 12:18 ` [patch net-next 03/15] mlxsw_core: register devlink port " Jiri Pirko
2023-05-25 12:36 ` Petr Machata
2023-05-24 12:18 ` [patch net-next 04/15] nfp: devlink: " Jiri Pirko
2023-05-24 12:18 ` [patch net-next 05/15] devlink: move port_split/unsplit() ops into devlink_port_ops Jiri Pirko
2023-05-24 17:32 ` Jesse Brandeburg
2023-05-25 4:53 ` Jakub Kicinski
2023-05-25 6:05 ` Jiri Pirko
2023-05-25 15:27 ` Jakub Kicinski
2023-05-25 16:53 ` Jiri Pirko
2023-05-25 12:37 ` Petr Machata
2023-05-24 12:18 ` [patch net-next 06/15] mlx4: register devlink port with ops Jiri Pirko
2023-05-24 12:18 ` [patch net-next 07/15] devlink: move port_type_set() op into devlink_port_ops Jiri Pirko
2023-05-24 12:18 ` [patch net-next 08/15] sfc: register devlink port with ops Jiri Pirko
2023-05-24 17:57 ` Alejandro Lucero Palau
2023-05-25 6:10 ` Jiri Pirko
2023-05-25 15:13 ` Alejandro Lucero Palau
2023-05-25 16:52 ` Jiri Pirko
2023-05-24 12:18 ` [patch net-next 09/15] mlx5: register devlink ports " Jiri Pirko
2023-05-24 12:18 ` [patch net-next 10/15] devlink: move port_fn_hw_addr_get/set() to devlink_port_ops Jiri Pirko
2023-05-24 12:18 ` [patch net-next 11/15] devlink: move port_fn_roce_get/set() " Jiri Pirko
2023-05-24 12:18 ` [patch net-next 12/15] devlink: move port_fn_migratable_get/set() " Jiri Pirko
2023-05-24 12:18 ` [patch net-next 13/15] devlink: move port_fn_state_get/set() " Jiri Pirko
2023-05-24 12:18 ` [patch net-next 14/15] devlink: move port_del() " Jiri Pirko
2023-05-24 12:18 ` [patch net-next 15/15] devlink: save devlink_port_ops into a variable in devlink_port_function_validate() Jiri Pirko
2023-05-25 4:55 ` Jakub Kicinski
2023-05-25 5:58 ` Jiri Pirko
2023-05-25 15:29 ` Jakub Kicinski
2023-05-26 8:53 ` Jiri Pirko
2023-05-24 14:02 ` [patch net-next 00/15] devlink: move port ops into separate structure Petr Machata
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=ZG77DAskJxpDYbdi@nanopsycho \
--to=jiri@resnulli.us \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=habetsm.xilinx@gmail.com \
--cc=idosch@nvidia.com \
--cc=jacob.e.keller@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=michal.wilczynski@intel.com \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=simon.horman@corigine.com \
--cc=tariqt@nvidia.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).