[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230416102833.GD15386@unreal>
Date: Sun, 16 Apr 2023 13:28:33 +0300
From: Leon Romanovsky <leon@...nel.org>
To: Jason Gunthorpe <jgg@...dia.com>
Cc: Jacob Keller <jacob.e.keller@...el.com>,
Avihai Horon <avihaih@...dia.com>, Aya Levin <ayal@...dia.com>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, linux-kernel@...r.kernel.org,
linux-rdma@...r.kernel.org, Meir Lichtinger <meirl@...lanox.com>,
Michael Guralnik <michaelgur@...lanox.com>,
netdev@...r.kernel.org, Paolo Abeni <pabeni@...hat.com>,
Saeed Mahameed <saeedm@...dia.com>,
Shay Drory <shayd@...dia.com>
Subject: Re: [PATCH rdma-next 0/4] Allow relaxed ordering read in VFs and VMs
On Thu, Apr 13, 2023 at 11:46:16AM -0300, Jason Gunthorpe wrote:
> On Thu, Apr 13, 2023 at 03:49:29PM +0300, Leon Romanovsky wrote:
>
> > > that it fixes a setup with VF and VM, so I think thats an ok thing to
> > > call out as the goal.
> >
> > VF or VM came from user perspective of where this behavior is not
> > correct. Avihai saw this in QEMU, so he described it in terms which
> > are more clear to the end user.
>
> Except it is not clear, the VF/VM issue is more properly solved by
> showing the real relaxed order cap to the VM.
I'm not convinced that patch restructure is really needed for something
so low as fix to problematic FW. I'm applying the series as is and
curious reader will read this discussion through Link tag from the
patch.
Thanks
Powered by blists - more mailing lists