[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YcOYDi1s5x5gU/5w@lunn.ch>
Date: Wed, 22 Dec 2021 22:26:38 +0100
From: Andrew Lunn <andrew@...n.ch>
To: "Chen, Mike Ximing" <mike.ximing.chen@...el.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"arnd@...db.de" <arnd@...db.de>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"Williams, Dan J" <dan.j.williams@...el.com>,
"pierre-louis.bossart@...ux.intel.com"
<pierre-louis.bossart@...ux.intel.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"davem@...emloft.net" <davem@...emloft.net>,
"kuba@...nel.org" <kuba@...nel.org>
Subject: Re: [RFC PATCH v12 01/17] dlb: add skeleton for DLB driver
> > pointing to skbufs? How are the lifetimes of skbufs managed? How do you get skbufs out of the NIC? Are
> > you using XDP?
>
> This is not a network accelerator in the sense that it does not have
> direct access to the network sockets/ports. We do not use XDP.
So not using XDP is a problem. I looked at previous versions of this
patch, and it is all DPDK. But DPDK is not in mainline, XDP is. In
order for this to be merged into mainline you need a mainline user of
it.
Maybe you should abandon mainline, and just get this driver merged
into the DPDK fork of Linux?
Andrew
Powered by blists - more mailing lists