[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPj3X_VQcnGwuG1OP4E4Qt=jwt_gStVigYS53BTVaL7PUnd4Jg@mail.gmail.com>
Date: Tue, 6 Feb 2024 12:16:13 -0800
From: Lee Duncan <lduncan@...e.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Alexander Lobakin <aleksander.lobakin@...el.com>, Chris Leech <cleech@...hat.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Nilesh Javali <njavali@...vell.com>,
Christoph Hellwig <hch@....de>, John Meneghini <jmeneghi@...hat.com>,
Mike Christie <michael.christie@...cle.com>, Hannes Reinecke <hare@...nel.org>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org,
GR-QLogic-Storage-Upstream@...vell.com
Subject: Re: [PATCH v5 0/4] UIO_MEM_DMA_COHERENT for cnic/bnx2/bnx2x
On Tue, Feb 6, 2024 at 7:54 AM Jakub Kicinski <kuba@...nel.org> wrote:
>
> On Mon, 5 Feb 2024 11:51:00 -0800 Chris Leech wrote:
> > > IIRC Jakub mentioned some time ago that he doesn't want to see
> > > third-party userspace <-> kernel space communication in the networking
> > > drivers, to me this looks exactly like that :z
> >
> > This isn't something anyone likes, but it's an interface that's been in
> > the kernel and in use since 2009. I'm trying to see if it can be fixed
> > "enough" to keep existing users functioning. If not, maybe the cnic
> > interface and the stacking protocol drivers (bnx2i/bnx2fc) should be
> > marked as broken.
>
> Yeah, is this one of the "converged Ethernet" monstrosities from
> the 2000s. All the companies which went deep into this stuff are
> now defunct AFAIK, and we're left holding the bag.
>
> Yay.
Actually, Marvel is around but seems loath to invest in re-architecting this
driver since it's so long in the tooth.
Powered by blists - more mailing lists