[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BYAPR11MB3095D6CC7DB2DC4E111561B1D96C9@BYAPR11MB3095.namprd11.prod.outlook.com>
Date: Mon, 15 Mar 2021 20:08:53 +0000
From: "Chen, Mike Ximing" <mike.ximing.chen@...el.com>
To: "Williams, Dan J" <dan.j.williams@...el.com>
CC: Greg KH <gregkh@...uxfoundation.org>,
Netdev <netdev@...r.kernel.org>,
David Miller <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
"Arnd Bergmann" <arnd@...db.de>,
Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
"Brandeburg, Jesse" <jesse.brandeburg@...el.com>
Subject: RE: [PATCH v10 00/20] dlb: introduce DLB device driver
> From: Dan Williams <dan.j.williams@...el.com>
> On Fri, Mar 12, 2021 at 1:55 PM Chen, Mike Ximing <mike.ximing.chen@...el.com> wrote:
> >
> > At its heart DLB consists of resources than can be assigned to
> > VDEVs/applications in a flexible manner, such as ports, queues,
> > credits to use queues, sequence numbers, etc.
>
> All of those objects are managed in userspace today in the unaccelerated case?
>
Yes, in the unaccelerated case, the software queue manager is generally implemented in the user space (except for cases like padata), so the resources are managed in the user space as well.
With a hardware DLB module, these resources will be managed by the kernel driver for VF and VDEV supports.
Thanks
Mike
Powered by blists - more mailing lists