From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102491] OpenCL app gets CL_OUT_OF_HOST_MEMORY on Cape Verde 7770
Date: Thu, 28 Dec 2017 13:08:08 +0000 [thread overview]
Message-ID: <bug-102491-502-YvAnQArZHP@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-102491-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 842 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=102491
--- Comment #5 from ka.nick@mail.ru ---
I managed to make it work somehow, but it's still unusable due to producing
artifacts on images processed using opencl on darktable and few other programs
I tried. So probably the title should be changed.
However, CL_OUT_OF_HOST_MEMORY error may be removed via envitonment var
setting, namely
export GPU_FORCE_64BIT_PTR=1
also
export GPU_USE_SYNC_OBJECTS=1
export GPU_MAX_ALLOC_PERCENT=100
export GPU_SINGLE_ALLOC_PERCENT=100
export GPU_MAX_HEAP_SIZE=100
are recommended but I haven't noticed any difference.
What I've noticed, however, is that the driver reports the different amount of
available GPU memory each time darktable is started...
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1611 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-12-28 13:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 8:33 [Bug 102491] OpenCL app gets CL_OUT_OF_HOST_MEMORY on Cape Verde 7770 bugzilla-daemon
2017-08-31 8:34 ` bugzilla-daemon
2017-08-31 8:34 ` bugzilla-daemon
2017-08-31 8:35 ` bugzilla-daemon
2017-08-31 8:37 ` bugzilla-daemon
2017-12-28 13:08 ` bugzilla-daemon [this message]
2017-12-28 13:09 ` [Bug 102491] OpenCL image processing produces artifacts " bugzilla-daemon
2019-11-19 7:58 ` 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-102491-502-YvAnQArZHP@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