Home
last modified time | relevance | path

Searched hist:"162 cca42920c2597298fcdf85538b40356c92151" (Results 1 – 6 of 6) sorted by relevance

/linux/drivers/net/ethernet/netronome/nfp/
H A Dnfp_port.cdiff 162cca42920c2597298fcdf85538b40356c92151 Tue Mar 15 07:00:06 CET 2022 Jakub Kicinski <kuba@kernel.org> eth: nfp: replace driver's "pf" lock with devlink instance lock

The whole reason for existence of the pf mutex is that we could
not lock the devlink instance around port splitting. There are
more types of reconfig which can make ports appear or disappear.
Now that the devlink instance lock is exposed to drivers and
"locked" helpers exist we can switch to using the devlink lock
directly.

Next patches will move the locking inside .port_(un)split to
the core.

Signed-off-by: Jakub Kicinski <kuba@kernel.org>
H A Dnfp_main.hdiff 162cca42920c2597298fcdf85538b40356c92151 Tue Mar 15 07:00:06 CET 2022 Jakub Kicinski <kuba@kernel.org> eth: nfp: replace driver's "pf" lock with devlink instance lock

The whole reason for existence of the pf mutex is that we could
not lock the devlink instance around port splitting. There are
more types of reconfig which can make ports appear or disappear.
Now that the devlink instance lock is exposed to drivers and
"locked" helpers exist we can switch to using the devlink lock
directly.

Next patches will move the locking inside .port_(un)split to
the core.

Signed-off-by: Jakub Kicinski <kuba@kernel.org>
H A Dnfp_app.hdiff 162cca42920c2597298fcdf85538b40356c92151 Tue Mar 15 07:00:06 CET 2022 Jakub Kicinski <kuba@kernel.org> eth: nfp: replace driver's "pf" lock with devlink instance lock

The whole reason for existence of the pf mutex is that we could
not lock the devlink instance around port splitting. There are
more types of reconfig which can make ports appear or disappear.
Now that the devlink instance lock is exposed to drivers and
"locked" helpers exist we can switch to using the devlink lock
directly.

Next patches will move the locking inside .port_(un)split to
the core.

Signed-off-by: Jakub Kicinski <kuba@kernel.org>
H A Dnfp_devlink.cdiff 162cca42920c2597298fcdf85538b40356c92151 Tue Mar 15 07:00:06 CET 2022 Jakub Kicinski <kuba@kernel.org> eth: nfp: replace driver's "pf" lock with devlink instance lock

The whole reason for existence of the pf mutex is that we could
not lock the devlink instance around port splitting. There are
more types of reconfig which can make ports appear or disappear.
Now that the devlink instance lock is exposed to drivers and
"locked" helpers exist we can switch to using the devlink lock
directly.

Next patches will move the locking inside .port_(un)split to
the core.

Signed-off-by: Jakub Kicinski <kuba@kernel.org>
H A Dnfp_net_main.cdiff 162cca42920c2597298fcdf85538b40356c92151 Tue Mar 15 07:00:06 CET 2022 Jakub Kicinski <kuba@kernel.org> eth: nfp: replace driver's "pf" lock with devlink instance lock

The whole reason for existence of the pf mutex is that we could
not lock the devlink instance around port splitting. There are
more types of reconfig which can make ports appear or disappear.
Now that the devlink instance lock is exposed to drivers and
"locked" helpers exist we can switch to using the devlink lock
directly.

Next patches will move the locking inside .port_(un)split to
the core.

Signed-off-by: Jakub Kicinski <kuba@kernel.org>
H A Dnfp_main.cdiff 162cca42920c2597298fcdf85538b40356c92151 Tue Mar 15 07:00:06 CET 2022 Jakub Kicinski <kuba@kernel.org> eth: nfp: replace driver's "pf" lock with devlink instance lock

The whole reason for existence of the pf mutex is that we could
not lock the devlink instance around port splitting. There are
more types of reconfig which can make ports appear or disappear.
Now that the devlink instance lock is exposed to drivers and
"locked" helpers exist we can switch to using the devlink lock
directly.

Next patches will move the locking inside .port_(un)split to
the core.

Signed-off-by: Jakub Kicinski <kuba@kernel.org>