From: Greg KH <gregkh@linuxfoundation.org>
To: Oded Gabbay <oded.gabbay@gmail.com>
Cc: linux-kernel@vger.kernel.org, oshpigelman@habana.ai, ttayar@habana.ai
Subject: Re: [PATCH v3 0/7] habanalabs: support info queries by multiple processes
Date: Wed, 31 Jul 2019 15:02:41 +0200 [thread overview]
Message-ID: <20190731130241.GC7590@kroah.com> (raw)
In-Reply-To: <20190731125901.20709-1-oded.gabbay@gmail.com>
On Wed, Jul 31, 2019 at 03:58:54PM +0300, Oded Gabbay wrote:
> v3 introduces a few fixes and changes the control char device's minor
> number to be 1 above that of the main device.
>
> Original text:
>
> Today, the driver allows only a single user application (the deep-learning
> application) to perform queries of the device's stats, information, idle
> state and more.
>
> This is a serious limitation in data centers, where there are
> multiple system/monitorining applications that want to continuously
> retrieve that information, while allowing the deep-learning application to
> perform work on the device.
>
> This patch-set allows unlimited number of user applications to perform
> the above queries (by calling the INFO IOCTL), while the deep-learning
> application is running.
>
> This is done by creating an additional char device per ASIC, that is
> dedicated to information retrieval only (allows only to call the INFO
> IOCTL). This method will maintain backward compatibility with existing
> userspace applications.
>
> - Patches 1-4 makes small improvements to existing code.
> - Patch 5 removes the accounting of the number of open file-descriptors
> and replace it with tracking of the driver's internal file private data
> strcuture.
> - Patch 6 is a pre-requisite to creating the two char devices
> - Patch 7 introduce the additional char device
>
> Thanks,
> Oded
>
> Oded Gabbay (7):
> habanalabs: add handle field to context structure
> habanalabs: kill user process after CS rollback
> habanalabs: show the process context dram usage
> habanalabs: rename user_ctx as compute_ctx
> habanalabs: maintain a list of file private data objects
> habanalabs: change device_setup_cdev() to be more generic
> habanalabs: create two char devices per ASIC
Whole series is:
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
prev parent reply other threads:[~2019-07-31 13:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 12:58 [PATCH v3 0/7] habanalabs: support info queries by multiple processes Oded Gabbay
2019-07-31 12:58 ` [PATCH v3 1/7] habanalabs: add handle field to context structure Oded Gabbay
2019-07-31 12:58 ` [PATCH v3 2/7] habanalabs: kill user process after CS rollback Oded Gabbay
2019-07-31 12:58 ` [PATCH v3 3/7] habanalabs: show the process context dram usage Oded Gabbay
2019-07-31 12:58 ` [PATCH v3 4/7] habanalabs: rename user_ctx as compute_ctx Oded Gabbay
2019-07-31 12:58 ` [PATCH v3 5/7] habanalabs: maintain a list of file private data objects Oded Gabbay
2019-07-31 12:59 ` [PATCH v3 6/7] habanalabs: change device_setup_cdev() to be more generic Oded Gabbay
2019-07-31 12:59 ` [PATCH v3 7/7] habanalabs: create two char devices per ASIC Oded Gabbay
2019-07-31 13:02 ` Greg KH
2019-07-31 13:02 ` 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=20190731130241.GC7590@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oded.gabbay@gmail.com \
--cc=oshpigelman@habana.ai \
--cc=ttayar@habana.ai \
/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