[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y5CU81h+NDjUVVSJ@nanopsycho>
Date: Wed, 7 Dec 2022 14:28:19 +0100
From: Jiri Pirko <jiri@...nulli.us>
To: Jakub Kicinski <kuba@...nel.org>
Cc: netdev@...r.kernel.org, davem@...emloft.net, pabeni@...hat.com,
edumazet@...gle.com, michael.chan@...adcom.com,
ioana.ciornei@....com, dmichail@...gible.com,
jesse.brandeburg@...el.com, anthony.l.nguyen@...el.com,
tchornyi@...vell.com, tariqt@...dia.com, saeedm@...dia.com,
leon@...nel.org, idosch@...dia.com, petrm@...dia.com,
vladimir.oltean@....com, claudiu.manoil@....com,
alexandre.belloni@...tlin.com, simon.horman@...igine.com,
shannon.nelson@....com, brett.creeley@....com
Subject: Re: [patch net-next 0/8] devlink: make sure devlink port
registers/unregisters only for registered instance
Tue, Dec 06, 2022 at 09:12:26PM CET, kuba@...nel.org wrote:
>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.
Sure, no problem.
Powered by blists - more mailing lists