Hey Joe,
I don't have all the answers right now but one thing I want to mention
is that, with cgroup, there's always a possibility for a user
configuration that lead to under resource for the application. Your
comments certainly highlight the needs to make under-resource
situation obvious to
> -Original Message-
> From: Kenny Ho
> Sent: Friday, November 29, 2019 12:00 AM
>
> Reducing audience since this is AMD specific.
>
> On Tue, Oct 8, 2019 at 3:11 PM Kuehling, Felix wrote:
> >
> > On 2019-08-29 2:05 a.m., Kenny Ho wrote:
> > > The number of logical gpu (lgpu) is
Reducing audience since this is AMD specific.
On Tue, Oct 8, 2019 at 3:11 PM Kuehling, Felix wrote:
>
> On 2019-08-29 2:05 a.m., Kenny Ho wrote:
> > The number of logical gpu (lgpu) is defined to be the number of compute
> > unit (CU) for a device. The lgpu allocation limit only applies to
> >
On 2019-08-29 2:05 a.m., Kenny Ho wrote:
> The number of logical gpu (lgpu) is defined to be the number of compute
> unit (CU) for a device. The lgpu allocation limit only applies to
> compute workload for the moment (enforced via kfd queue creation.) Any
> cu_mask update is validated against
The number of logical gpu (lgpu) is defined to be the number of compute
unit (CU) for a device. The lgpu allocation limit only applies to
compute workload for the moment (enforced via kfd queue creation.) Any
cu_mask update is validated against the availability of the compute unit
as defined by
