From: Jakub Kicinski <kuba@kernel•org>
To: Jiri Pirko <jiri@resnulli•us>
Cc: netdev@vger•kernel.org, davem@davemloft•net, pabeni@redhat•com,
edumazet@google•com, michael.chan@broadcom•com,
ioana.ciornei@nxp•com, dmichail@fungible•com,
jesse.brandeburg@intel•com, anthony.l.nguyen@intel•com,
tchornyi@marvell•com, tariqt@nvidia•com, saeedm@nvidia•com,
leon@kernel•org, idosch@nvidia•com, petrm@nvidia•com,
vladimir.oltean@nxp•com, claudiu.manoil@nxp•com,
alexandre.belloni@bootlin•com, simon.horman@corigine•com,
shannon.nelson@amd•com, brett.creeley@amd•com
Subject: Re: [patch net-next 0/8] devlink: make sure devlink port registers/unregisters only for registered instance
Date: Tue, 6 Dec 2022 12:12:26 -0800 [thread overview]
Message-ID: <20221206121226.21de7ca3@kernel.org> (raw)
In-Reply-To: <Y47y0FZQxPDK3B5X@nanopsycho>
On Tue, 6 Dec 2022 08:44:16 +0100 Jiri Pirko wrote:
>> I didn't reply because I don't have much to add beyond what
>> I've already said too many times. I prefer to move to my
>> initial full refcounting / full locking design. I haven't posted
>> any patches because I figured it's too low priority and too risky
>> to be doing right before the merge window.
>
> I'm missing how what you describe is relevant to this patchset and to
> the issue it is trying to solve :/
>
>> I agree that reordering is a good idea but not as a fix, and hopefully
>
> I don't see other way to fix the netdev/devlink events ordering problem
> I described above. Do you?
Just hold off with your patches until I post mine. Which as I said will
be during/after the merge window. I've been explaining this for a year now.
next prev parent reply other threads:[~2022-12-06 20:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 15:22 [patch net-next 0/8] devlink: make sure devlink port registers/unregisters only for registered instance Jiri Pirko
2022-12-05 15:22 ` [patch net-next 1/8] devlink: call devlink_port_register/unregister() on " Jiri Pirko
2022-12-05 23:55 ` Shannon Nelson
2022-12-06 7:41 ` Jiri Pirko
2022-12-06 7:56 ` Leon Romanovsky
2022-12-06 17:35 ` Shannon Nelson
2022-12-07 13:27 ` Jiri Pirko
2022-12-07 19:45 ` Shannon Nelson
2022-12-05 15:22 ` [patch net-next 2/8] netdevsim: call devl_port_register/unregister() " Jiri Pirko
2022-12-05 15:22 ` [patch net-next 3/8] mlxsw: " Jiri Pirko
2022-12-05 15:22 ` [patch net-next 4/8] nfp: " Jiri Pirko
2022-12-05 15:22 ` [patch net-next 5/8] mlx4: " Jiri Pirko
2022-12-05 15:22 ` [patch net-next 6/8] mlx5: " Jiri Pirko
2022-12-05 15:22 ` [patch net-next 7/8] devlink: assert if devl_port_register/unregister() is called on unregistered devlink instance Jiri Pirko
2022-12-05 15:22 ` [patch net-next 8/8] devlink: remove port notifications from devlink_register/unregister() Jiri Pirko
2022-12-06 1:08 ` [patch net-next 0/8] devlink: make sure devlink port registers/unregisters only for registered instance Jakub Kicinski
2022-12-06 7:44 ` Jiri Pirko
2022-12-06 20:12 ` Jakub Kicinski [this message]
2022-12-07 13:28 ` Jiri Pirko
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=20221206121226.21de7ca3@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=alexandre.belloni@bootlin$(echo .)com \
--cc=anthony.l.nguyen@intel$(echo .)com \
--cc=brett.creeley@amd$(echo .)com \
--cc=claudiu.manoil@nxp$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=dmichail@fungible$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=idosch@nvidia$(echo .)com \
--cc=ioana.ciornei@nxp$(echo .)com \
--cc=jesse.brandeburg@intel$(echo .)com \
--cc=jiri@resnulli$(echo .)us \
--cc=leon@kernel$(echo .)org \
--cc=michael.chan@broadcom$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=petrm@nvidia$(echo .)com \
--cc=saeedm@nvidia$(echo .)com \
--cc=shannon.nelson@amd$(echo .)com \
--cc=simon.horman@corigine$(echo .)com \
--cc=tariqt@nvidia$(echo .)com \
--cc=tchornyi@marvell$(echo .)com \
--cc=vladimir.oltean@nxp$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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