From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103697] [regression] shared memory size 64k -> 32k?
Date: Mon, 13 Nov 2017 15:33:59 +0000 [thread overview]
Message-ID: <bug-103697-502-6FH8wQBlVT@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-103697-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 667 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=103697
--- Comment #2 from O Heid <oliver.heid@h-next.de> ---
I checked back with AMD and they say that there is hardware support for 64kB
shared memory. This actually gets exposed in OpenCL and ROCm/HC.
The 2016 AMD GCN3 manual wrongly states it is only 32kB, but the AMD Vega ISA
reference guide has the correct 64kB LDS size.
So it seems the restriction is due to the mesa software stack, not due to
hardware. Could you please raise the bar back to 64kB? I wouldn't ask if it
wouldn't hit me with with a 2x performance penalty...
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1496 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-11-13 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-103697-502@http.bugs.freedesktop.org/>
2017-11-12 15:09 ` [Bug 103697] [regression] shared memory size 64k -> 32k? bugzilla-daemon
2017-11-12 22:39 ` bugzilla-daemon
2017-11-13 15:33 ` bugzilla-daemon [this message]
2017-11-28 14:54 ` bugzilla-daemon
2017-11-28 16:41 ` bugzilla-daemon
2017-12-19 8:45 ` 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-103697-502-6FH8wQBlVT@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 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).