From: Kenny Ho <y2kenny@gmail.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: "Kenny Ho" <Kenny.Ho@amd.com>,
"Kuehling, Felix" <felix.kuehling@amd.com>,
jsparks@cray.com, dri-devel <dri-devel@lists.freedesktop.org>,
lkaplan@cray.com, "Alex Deucher" <alexander.deucher@amd.com>,
"amd-gfx list" <amd-gfx@lists.freedesktop.org>,
"Greathouse, Joseph" <joseph.greathouse@amd.com>,
"Tejun Heo" <tj@kernel.org>,
cgroups@vger.kernel.org,
"Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH v2 00/11] new cgroup controller for gpu/drm subsystem
Date: Tue, 14 Apr 2020 09:14:27 -0400 [thread overview]
Message-ID: <CAOWid-fwEOk+4CvUAumo=byWpq4vVUoCiwW1N6F-0aEd6G7d4A@mail.gmail.com> (raw)
In-Reply-To: <CAKMK7uEs5QvUrxKcTFksO30D+x=XJnV+_TA-ebawcihtLqDG0Q@mail.gmail.com>
Ok. I was hoping you can clarify the contradiction between the
existance of the spec below and your "not something any other gpu can
reasonably support" statement. I mean, OneAPI is Intel's spec and
doesn't that at least make SubDevice support "reasonable" for one more
vendor?
Partisanship aside, as a drm co-maintainer, do you really not see the
need for non-work-conserving way of distributing GPU as a resource?
You recognized the latencies involved (although that's really just
part of the story... time sharing is never going to be good enough
even if your switching cost is zero.) As a drm co-maintainer, are you
suggesting GPU has no place in the HPC use case?
Regards,
Kenny
On Tue, Apr 14, 2020 at 8:52 AM Daniel Vetter <daniel@ffwll.ch> wrote:
>
> On Tue, Apr 14, 2020 at 2:47 PM Kenny Ho <y2kenny@gmail.com> wrote:
> > On Tue, Apr 14, 2020 at 8:20 AM Daniel Vetter <daniel@ffwll.ch> wrote:
> > > My understanding from talking with a few other folks is that
> > > the cpumask-style CU-weight thing is not something any other gpu can
> > > reasonably support (and we have about 6+ of those in-tree)
> >
> > How does Intel plan to support the SubDevice API as described in your
> > own spec here:
> > https://spec.oneapi.com/versions/0.7/oneL0/core/INTRO.html#subdevice-support
>
> I can't talk about whether future products might or might not support
> stuff and in what form exactly they might support stuff or not support
> stuff. Or why exactly that's even in the spec there or not.
>
> Geez
> -Daniel
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Kenny Ho <y2kenny@gmail.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: "Kenny Ho" <Kenny.Ho@amd.com>,
"Kuehling, Felix" <felix.kuehling@amd.com>,
jsparks@cray.com, dri-devel <dri-devel@lists.freedesktop.org>,
lkaplan@cray.com, "Alex Deucher" <alexander.deucher@amd.com>,
"amd-gfx list" <amd-gfx@lists.freedesktop.org>,
"Greathouse, Joseph" <joseph.greathouse@amd.com>,
"Tejun Heo" <tj@kernel.org>,
cgroups@vger.kernel.org,
"Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH v2 00/11] new cgroup controller for gpu/drm subsystem
Date: Tue, 14 Apr 2020 09:14:27 -0400 [thread overview]
Message-ID: <CAOWid-fwEOk+4CvUAumo=byWpq4vVUoCiwW1N6F-0aEd6G7d4A@mail.gmail.com> (raw)
In-Reply-To: <CAKMK7uEs5QvUrxKcTFksO30D+x=XJnV+_TA-ebawcihtLqDG0Q@mail.gmail.com>
Ok. I was hoping you can clarify the contradiction between the
existance of the spec below and your "not something any other gpu can
reasonably support" statement. I mean, OneAPI is Intel's spec and
doesn't that at least make SubDevice support "reasonable" for one more
vendor?
Partisanship aside, as a drm co-maintainer, do you really not see the
need for non-work-conserving way of distributing GPU as a resource?
You recognized the latencies involved (although that's really just
part of the story... time sharing is never going to be good enough
even if your switching cost is zero.) As a drm co-maintainer, are you
suggesting GPU has no place in the HPC use case?
Regards,
Kenny
On Tue, Apr 14, 2020 at 8:52 AM Daniel Vetter <daniel@ffwll.ch> wrote:
>
> On Tue, Apr 14, 2020 at 2:47 PM Kenny Ho <y2kenny@gmail.com> wrote:
> > On Tue, Apr 14, 2020 at 8:20 AM Daniel Vetter <daniel@ffwll.ch> wrote:
> > > My understanding from talking with a few other folks is that
> > > the cpumask-style CU-weight thing is not something any other gpu can
> > > reasonably support (and we have about 6+ of those in-tree)
> >
> > How does Intel plan to support the SubDevice API as described in your
> > own spec here:
> > https://spec.oneapi.com/versions/0.7/oneL0/core/INTRO.html#subdevice-support
>
> I can't talk about whether future products might or might not support
> stuff and in what form exactly they might support stuff or not support
> stuff. Or why exactly that's even in the spec there or not.
>
> Geez
> -Daniel
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Kenny Ho <y2kenny-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Daniel Vetter <daniel-/w4YWyX8dFk@public.gmane.org>
Cc: "Kenny Ho" <Kenny.Ho-5C7GfCeVMHo@public.gmane.org>,
"Kuehling, Felix" <felix.kuehling-5C7GfCeVMHo@public.gmane.org>,
jsparks-WVYJKLFxKCc@public.gmane.org,
dri-devel
<dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
lkaplan-WVYJKLFxKCc@public.gmane.org,
"Alex Deucher" <alexander.deucher-5C7GfCeVMHo@public.gmane.org>,
"amd-gfx list"
<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
"Greathouse,
Joseph" <joseph.greathouse-5C7GfCeVMHo@public.gmane.org>,
"Tejun Heo" <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"Christian König" <christian.koenig-5C7GfCeVMHo@public.gmane.org>
Subject: Re: [PATCH v2 00/11] new cgroup controller for gpu/drm subsystem
Date: Tue, 14 Apr 2020 09:14:27 -0400 [thread overview]
Message-ID: <CAOWid-fwEOk+4CvUAumo=byWpq4vVUoCiwW1N6F-0aEd6G7d4A@mail.gmail.com> (raw)
In-Reply-To: <CAKMK7uEs5QvUrxKcTFksO30D+x=XJnV+_TA-ebawcihtLqDG0Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Ok. I was hoping you can clarify the contradiction between the
existance of the spec below and your "not something any other gpu can
reasonably support" statement. I mean, OneAPI is Intel's spec and
doesn't that at least make SubDevice support "reasonable" for one more
vendor?
Partisanship aside, as a drm co-maintainer, do you really not see the
need for non-work-conserving way of distributing GPU as a resource?
You recognized the latencies involved (although that's really just
part of the story... time sharing is never going to be good enough
even if your switching cost is zero.) As a drm co-maintainer, are you
suggesting GPU has no place in the HPC use case?
Regards,
Kenny
On Tue, Apr 14, 2020 at 8:52 AM Daniel Vetter <daniel-/w4YWyX8dFk@public.gmane.org> wrote:
>
> On Tue, Apr 14, 2020 at 2:47 PM Kenny Ho <y2kenny-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > On Tue, Apr 14, 2020 at 8:20 AM Daniel Vetter <daniel-/w4YWyX8dFk@public.gmane.org> wrote:
> > > My understanding from talking with a few other folks is that
> > > the cpumask-style CU-weight thing is not something any other gpu can
> > > reasonably support (and we have about 6+ of those in-tree)
> >
> > How does Intel plan to support the SubDevice API as described in your
> > own spec here:
> > https://spec.oneapi.com/versions/0.7/oneL0/core/INTRO.html#subdevice-support
>
> I can't talk about whether future products might or might not support
> stuff and in what form exactly they might support stuff or not support
> stuff. Or why exactly that's even in the spec there or not.
>
> Geez
> -Daniel
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2020-04-14 13:14 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <lkaplan@cray.com; daniel@ffwll.ch; nirmoy.das@amd.com; damon.mcdougall@amd.com; juan.zuniga-anaya@amd.com; hannes@cmpxchg.org>
2020-02-26 19:01 ` [PATCH v2 00/11] new cgroup controller for gpu/drm subsystem Kenny Ho
2020-02-26 19:01 ` Kenny Ho
2020-02-26 19:01 ` Kenny Ho
2020-02-26 19:01 ` [PATCH v2 01/11] cgroup: Introduce cgroup for drm subsystem Kenny Ho
2020-02-26 19:01 ` Kenny Ho
2020-02-26 19:01 ` Kenny Ho
2020-02-26 19:01 ` [PATCH v2 02/11] drm, cgroup: Bind drm and cgroup subsystem Kenny Ho
2020-02-26 19:01 ` Kenny Ho
2020-02-26 19:01 ` Kenny Ho
2020-02-26 19:01 ` [PATCH v2 03/11] drm, cgroup: Initialize drmcg properties Kenny Ho
2020-02-26 19:01 ` Kenny Ho
2020-02-26 19:01 ` Kenny Ho
2020-02-26 19:01 ` [PATCH v2 04/11] drm, cgroup: Add total GEM buffer allocation stats Kenny Ho
2020-02-26 19:01 ` Kenny Ho
2020-02-26 19:01 ` Kenny Ho
2020-02-26 19:01 ` [PATCH v2 05/11] drm, cgroup: Add peak " Kenny Ho
2020-02-26 19:01 ` Kenny Ho
2020-02-26 19:01 ` Kenny Ho
2020-02-26 19:01 ` [PATCH v2 06/11] drm, cgroup: Add GEM buffer allocation count stats Kenny Ho
2020-02-26 19:01 ` Kenny Ho
2020-02-26 19:01 ` Kenny Ho
2020-02-26 19:01 ` [PATCH v2 07/11] drm, cgroup: Add total GEM buffer allocation limit Kenny Ho
2020-02-26 19:01 ` Kenny Ho
2020-02-26 19:01 ` Kenny Ho
2020-02-26 19:01 ` [PATCH v2 08/11] drm, cgroup: Add peak " Kenny Ho
2020-02-26 19:01 ` Kenny Ho
2020-02-26 19:01 ` Kenny Ho
2020-02-26 19:01 ` [PATCH v2 09/11] drm, cgroup: Add compute as gpu cgroup resource Kenny Ho
2020-02-26 19:01 ` Kenny Ho
2020-02-26 19:01 ` Kenny Ho
2020-02-26 19:01 ` [PATCH v2 10/11] drm, cgroup: add update trigger after limit change Kenny Ho
2020-02-26 19:01 ` Kenny Ho
2020-02-26 19:01 ` Kenny Ho
2020-02-26 19:01 ` [PATCH v2 11/11] drm/amdgpu: Integrate with DRM cgroup Kenny Ho
2020-02-26 19:01 ` Kenny Ho
2020-02-26 19:01 ` Kenny Ho
2020-03-17 16:03 ` [PATCH v2 00/11] new cgroup controller for gpu/drm subsystem Kenny Ho
2020-03-17 16:03 ` Kenny Ho
2020-03-17 16:03 ` Kenny Ho
2020-03-24 18:46 ` Tejun Heo
2020-03-24 18:46 ` Tejun Heo
2020-03-24 18:46 ` Tejun Heo
2020-03-24 18:49 ` Kenny Ho
2020-03-24 18:49 ` Kenny Ho
2020-03-24 18:49 ` Kenny Ho
2020-04-13 19:11 ` Tejun Heo
2020-04-13 19:11 ` Tejun Heo
2020-04-13 19:11 ` Tejun Heo
2020-04-13 20:12 ` Ho, Kenny
2020-04-13 20:12 ` Ho, Kenny
2020-04-13 20:12 ` Ho, Kenny
2020-04-13 20:17 ` Kenny Ho
2020-04-13 20:17 ` Kenny Ho
2020-04-13 20:17 ` Kenny Ho
2020-04-13 20:54 ` Tejun Heo
2020-04-13 20:54 ` Tejun Heo
2020-04-13 20:54 ` Tejun Heo
2020-04-13 21:40 ` Kenny Ho
2020-04-13 21:40 ` Kenny Ho
2020-04-13 21:40 ` Kenny Ho
2020-04-13 21:53 ` Tejun Heo
2020-04-13 21:53 ` Tejun Heo
2020-04-13 21:53 ` Tejun Heo
2020-04-14 12:20 ` Daniel Vetter
2020-04-14 12:20 ` Daniel Vetter
2020-04-14 12:20 ` Daniel Vetter
2020-04-14 12:47 ` Kenny Ho
2020-04-14 12:47 ` Kenny Ho
2020-04-14 12:47 ` Kenny Ho
2020-04-14 12:52 ` Daniel Vetter
2020-04-14 12:52 ` Daniel Vetter
2020-04-14 12:52 ` Daniel Vetter
2020-04-14 13:14 ` Kenny Ho [this message]
2020-04-14 13:14 ` Kenny Ho
2020-04-14 13:14 ` Kenny Ho
2020-04-14 13:26 ` Daniel Vetter
2020-04-14 13:26 ` Daniel Vetter
2020-04-14 13:26 ` Daniel Vetter
2020-04-14 13:50 ` Kenny Ho
2020-04-14 13:50 ` Kenny Ho
2020-04-14 13:50 ` Kenny Ho
2020-04-14 14:04 ` Daniel Vetter
2020-04-14 14:04 ` Daniel Vetter
2020-04-14 14:04 ` Daniel Vetter
2020-04-14 14:29 ` Kenny Ho
2020-04-14 14:29 ` Kenny Ho
2020-04-14 14:29 ` Kenny Ho
2020-04-14 15:01 ` Daniel Vetter
2020-04-14 15:01 ` Daniel Vetter
2020-04-14 15:01 ` Daniel Vetter
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='CAOWid-fwEOk+4CvUAumo=byWpq4vVUoCiwW1N6F-0aEd6G7d4A@mail.gmail.com' \
--to=y2kenny@gmail.com \
--cc=Kenny.Ho@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=cgroups@vger.kernel.org \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=felix.kuehling@amd.com \
--cc=joseph.greathouse@amd.com \
--cc=jsparks@cray.com \
--cc=lkaplan@cray.com \
--cc=tj@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.