From: Omer Shpigelman <oshpigelman@habana.ai>
To: Oded Gabbay <oded.gabbay@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Tomer Tayar <ttayar@habana.ai>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Subject: RE: [PATCH 4/6] habanalabs: increase max jobs number to 512
Date: Mon, 11 Nov 2019 06:03:15 +0000 [thread overview]
Message-ID: <AM6PR0202MB338239BB13CB3245480B1CA4B8740@AM6PR0202MB3382.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <20191110215533.754-4-oded.gabbay@gmail.com>
On Sun, Nov 10, 2019 at 11:56 PM Oded Gabbay wrote:
> In training, there is a need for a large amount of patching to the recipe.
> This results in many command buffers contains a lot of DMA packets. The
> number of command buffers per CS is larger than the current maximum of
> 64, which is an arbitrary number that is enough for inference, but it has no
> real affect on the code and/or resources of the host machine.
>
> Signed-off-by: Oded Gabbay <oded.gabbay@gmail.com>
Reviewed-by: Omer Shpigelman <oshpigelman@habana.ai>
next prev parent reply other threads:[~2019-11-11 6:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-10 21:55 [PATCH 1/6] habanalabs: read F/W versions before failure Oded Gabbay
2019-11-10 21:55 ` [PATCH 2/6] habanalabs: use registers name defines for ETR block Oded Gabbay
2019-11-11 5:59 ` Omer Shpigelman
2019-11-10 21:55 ` [PATCH 3/6] habanalabs: set ETR as non-secured Oded Gabbay
2019-11-11 6:01 ` Omer Shpigelman
2019-11-10 21:55 ` [PATCH 4/6] habanalabs: increase max jobs number to 512 Oded Gabbay
2019-11-11 6:03 ` Omer Shpigelman [this message]
2019-11-10 21:55 ` [PATCH 5/6] habanalabs: don't print error when queues are full Oded Gabbay
2019-11-11 6:04 ` Omer Shpigelman
2019-11-10 21:55 ` [PATCH 6/6] habanalabs: export uapi defines to user-space Oded Gabbay
2019-11-11 6:08 ` Omer Shpigelman
2019-11-11 5:56 ` [PATCH 1/6] habanalabs: read F/W versions before failure Omer Shpigelman
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=AM6PR0202MB338239BB13CB3245480B1CA4B8740@AM6PR0202MB3382.eurprd02.prod.outlook.com \
--to=oshpigelman@habana.ai \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oded.gabbay@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).