From: Nirmoy <nirmodas@amd.com>
To: Nirmoy Das <nirmoy.aiemd@gmail.com>, amd-gfx@lists.freedesktop.org
Cc: alexander.deucher@amd.com, Ray.Huang@amd.com, nirmoy.das@amd.com,
christian.koenig@amd.com
Subject: Re: [RFC PATCH 1/4] drm/amdgpu: set compute queue priority at mqd_init
Date: Thu, 27 Feb 2020 22:42:57 +0100 [thread overview]
Message-ID: <c076c65e-cd7b-2cda-44b5-70a54d039ddf@amd.com> (raw)
In-Reply-To: <20200227214012.3383-1-nirmoy.das@amd.com>
On 2/27/20 10:40 PM, Nirmoy Das wrote:
> We were changing compute ring priority while rings were being used
> before every job submission which is not recommended. This patch
> sets compute queue priority at mqd initialization for gfx8 and gfx9.
>
> Policy: Enable high priority compute queues only if gpu has >1 MEC, if
> so PIPE0 and PIPE1 will be in high priority.
s/PIPE0 and PIPE1 will be in high priority/ 1st queue of each pipe will
set to high priority
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2020-02-27 21:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 21:40 [RFC PATCH 1/4] drm/amdgpu: set compute queue priority at mqd_init Nirmoy Das
2020-02-27 21:40 ` [RFC PATCH 2/4] drm/scheduler: implement a function to modify sched list Nirmoy Das
2020-02-28 5:08 ` Luben Tuikov
2020-02-28 7:47 ` Christian König
2020-02-28 9:30 ` Nirmoy
2020-03-02 20:47 ` Luben Tuikov
2020-03-03 19:06 ` Christian König
2020-03-03 20:04 ` Luben Tuikov
2020-02-27 21:40 ` [RFC PATCH 3/4] drm/amdgpu: change hw sched list on ctx priority override Nirmoy Das
2020-02-28 4:17 ` Luben Tuikov
2020-02-27 21:40 ` [RFC PATCH 4/4] drm/amdgpu: remove unused functions Nirmoy Das
2020-02-27 21:42 ` Nirmoy [this message]
2020-02-27 21:48 ` [RFC PATCH 1/4] drm/amdgpu: set compute queue priority at mqd_init Alex Deucher
2020-02-27 21:50 ` Alex Deucher
2020-02-27 21:56 ` Das, Nirmoy
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=c076c65e-cd7b-2cda-44b5-70a54d039ddf@amd.com \
--to=nirmodas@amd.com \
--cc=Ray.Huang@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=nirmoy.aiemd@gmail.com \
--cc=nirmoy.das@amd.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 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.