From: Greg KH <gregkh@linuxfoundation.org>
To: Guy Zadicario <guy.zadicario@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"olof@lixom.net" <olof@lixom.net>,
"alexander.shishkin@linux.intel.com"
<alexander.shishkin@linux.intel.com>,
"Shevchenko, Andriy" <andriy.shevchenko@intel.com>,
"Shefi-simchon, Yochai" <yochai.shefi-simchon@intel.com>
Subject: Re: [PATCH v2 00/15] misc: nnpi: New PCIe driver for Intel's NNP-I pcie device
Date: Tue, 15 Jun 2021 17:54:16 +0200 [thread overview]
Message-ID: <YMjNKAojoGsQ8Z9J@kroah.com> (raw)
In-Reply-To: <20210615145755.GA25911@aipg-stp-03.iil.intel.com>
On Tue, Jun 15, 2021 at 05:58:09PM +0300, Guy Zadicario wrote:
> On Fri, May 14, 2021 at 11:33:31AM +0300, Greg KH wrote:
> > On Thu, May 13, 2021 at 11:57:10AM +0300, Guy Zadicario wrote:
> > > Hi,
> > >
> > > The following series is a driver for a new PCIe device from Intel named NNP-I
> > > (Nirvana Neural Processor for Inference). NNP-I is a PCIe connected compute
> > > device used for acceleration of AI deep learning inference applications in the
> > > data-center.
> >
> > How does this differ from the "intel_gna" driver being proposed here:
> > https://lore.kernel.org/linux-doc/20210513110040.2268-1-maciej.kwapulinski@linux.intel.com/
> >
> > Please work together to come up with a unified userspace api for these
> > devices, and hopefully, shared kernel code as well.
> >
> Ok, after consulting, we will try to share api and some kernel code
> between the two drivers.
>
> The plan is to suggest a common framework for both devices
> and let each device driver register with that framework,
> some functionality will be common and some will be device driver
> specific (same model as drm for gpus). At first I think the common part
> will be small and will deal only with host memory management, later,
> it might grow, if/when some other drivers will adopt it as well.
>
> We will first change the NNP-I driver to use this framework.
> The GNA driver will wait for this API to be accepted and only then will
> adopt it and request to upstream.
Great, can you also look into what it would take to move the habanna
code to this new api as well? A new api doesn't mean much if there is
only one user :)
thanks,
greg k-h
prev parent reply other threads:[~2021-06-15 15:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 8:57 Guy Zadicario
2021-05-13 8:57 ` [PATCH v2 01/15] misc: nnpi: Document NNP-I's driver overview Guy Zadicario
2021-05-13 8:57 ` [PATCH v2 02/15] misc: nnpi: Initialize NNP-I framework and PCIe modules Guy Zadicario
2021-05-13 8:57 ` [PATCH v2 03/15] misc: nnpi: Manage and schedule messages to device Guy Zadicario
2021-05-13 8:57 ` [PATCH v2 04/15] misc: nnpi: Define host/card ipc protocol Guy Zadicario
2021-05-13 8:57 ` [PATCH v2 05/15] misc: nnpi: Manage host memory resources Guy Zadicario
2021-05-13 8:57 ` [PATCH v2 06/15] misc: nnpi: Allow usermode to manage host resources Guy Zadicario
2021-05-17 7:02 ` Dave Airlie
2021-05-13 8:57 ` [PATCH v2 07/15] misc: nnpi: Disallow host memory resource access if no NNP-I devices exist Guy Zadicario
2021-05-13 8:57 ` [PATCH v2 08/15] misc: nnpi: Boot NNP-I device Guy Zadicario
2021-05-13 8:57 ` [PATCH v2 09/15] misc: nnpi: Process device response messages Guy Zadicario
2021-05-13 8:57 ` [PATCH v2 10/15] misc: nnpi: Query and verify device protocol Guy Zadicario
2021-05-13 8:57 ` [PATCH v2 11/15] misc: nnpi: Create comm channel from app to device Guy Zadicario
2021-05-13 8:57 ` [PATCH v2 12/15] misc: nnpi: Route device response messages Guy Zadicario
2021-05-13 8:57 ` [PATCH v2 13/15] misc: nnpi: Expose command channel file interface Guy Zadicario
2021-05-13 8:57 ` [PATCH v2 14/15] misc: nnpi: Create command channel from userspace Guy Zadicario
2021-05-13 8:57 ` [PATCH v2 15/15] misc: nnpi: Map host resources to device channel Guy Zadicario
2021-05-14 8:33 ` [PATCH v2 00/15] misc: nnpi: New PCIe driver for Intel's NNP-I pcie device Greg KH
2021-06-15 14:58 ` Guy Zadicario
2021-06-15 15:54 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YMjNKAojoGsQ8Z9J@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=guy.zadicario@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=yochai.shefi-simchon@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®