From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110481] performance hot issues in amdgpu_cs_ib_vm_chunk
Date: Mon, 22 Apr 2019 02:50:57 +0000 [thread overview]
Message-ID: <bug-110481-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1115 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110481
Bug ID: 110481
Summary: performance hot issues in amdgpu_cs_ib_vm_chunk
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: baopeng88_com@163.com
We have encountered performance hot issues in vce module. Cpu occupancy rate
has been in the alloc_vmap_area function.
We found that calling the alloc_vmap_area function mainly occurs in the
amdgpu_cs_ib_vm_chunk function. So we removed the main loop judgment logic of
amdgpu_cs_ib_vm_chunk.
as follows .
- if (p->ring->funcs->parse_cs || p->ring->funcs->patch_cs_in_place) {
+ if (0)
If we don't delete, vce will be very slow.
Is this the fundamental way to solve the problem? Or there are other ways to
solve the problem?
3q very much.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2428 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-04-22 2:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-22 2:50 bugzilla-daemon [this message]
2019-04-22 3:48 ` [Bug 110481] performance hot issues in amdgpu_cs_ib_vm_chunk bugzilla-daemon
2019-04-23 13:03 ` bugzilla-daemon
2019-11-19 9:19 ` bugzilla-daemon
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=bug-110481-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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.