Date: Fri, 1 Sep 2017 18:42:01 +0300 From: Arto Pekkanen <isoa@kapsi.fi> To: Scott Bennett <bennett@sdf.org> Cc: freebsd-x11@freebsd.org Subject: Re: OpenCL/OpenGL contention on a device (was Re: x11/nvidia-driver-340 and OpenCL) Message-ID: <88a65451-d2ba-589d-20e0-9ff763ce9052@kapsi.fi> In-Reply-To: <201708310843.v7V8h7Nx006278@sdf.org> References: <201708241205.v7OC5wrR016229@sdf.org> <y3q5-l7c4-wny@FreeBSD.org> <201708271111.v7RBB7Z8005388@sdf.org> <8ti4-udq3-wny@FreeBSD.org> <201708281111.v7SBBVSf000652@sdf.org> <85a52dec-c20d-7869-7019-1564e034aad3@kapsi.fi> <201708310843.v7V8h7Nx006278@sdf.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --q1JrxXAiG6eEwGgOMeoKjDkJqmQ7kkU5l Content-Type: multipart/mixed; boundary="R4LCgSUlS2Fikn15sGD71OPlhB8X8521n"; protected-headers="v1" From: Arto Pekkanen <isoa@kapsi.fi> To: Scott Bennett <bennett@sdf.org> Cc: freebsd-x11@freebsd.org Message-ID: <88a65451-d2ba-589d-20e0-9ff763ce9052@kapsi.fi> Subject: Re: OpenCL/OpenGL contention on a device (was Re: x11/nvidia-driver-340 and OpenCL) References: <201708241205.v7OC5wrR016229@sdf.org> <y3q5-l7c4-wny@FreeBSD.org> <201708271111.v7RBB7Z8005388@sdf.org> <8ti4-udq3-wny@FreeBSD.org> <201708281111.v7SBBVSf000652@sdf.org> <85a52dec-c20d-7869-7019-1564e034aad3@kapsi.fi> <201708310843.v7V8h7Nx006278@sdf.org> In-Reply-To: <201708310843.v7V8h7Nx006278@sdf.org> --R4LCgSUlS2Fikn15sGD71OPlhB8X8521n Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable I was not talking about working sets that require all of the VRAM on the GPU. I was thinking of a situation where the computing jobs use only a portion of memory, leaving plenty available for graphics operations. In that case me and my friends haven't seen any stuttering on most mid-tier nVidia and AMD cards. I might try running a VRAM hogging computing job on my Windows box, but I assume the driver is smart enough to prioritize graphics resources over computing resources in VRAM and limit the number of fetches from RAM on computing kernels to prevent bus saturation etc. On 31.8.2017 11:43, Scott Bennett wrote: > Arto Pekkanen <isoa@kapsi.fi> wrote: >=20 >> If the GPU driver is implemented properly there will be no stutter or >> other problems even when running OpenCL jobs. >=20 > Really! So an OpenCL work item that needs, say, nearly all the av= ailable > memory on a graphics device and a 3D shader that has similar memory > requirements will not interfere with each other? That seems rather mag= ical > somehow, even if the OpenGL stuff always has a higher priority inside t= he GPU > than the OpenCL stuff. >> >> In Windows there is no problem running OpenCL jobs on the same device >> that operates your display. Like running a crypto currency miner while= >> browsing the web. Playing games won't work well, but basic stuff you c= an do. >> > Is that partly because the memory requirements of the "basic stuff= " are > typically tiny when compared to the capacity of today's graphics device= s? >=20 >> TL;DR when the FreeBSD GPU driver and all the userland bits are up to >> date, I'd expect there to be no issues with stuttering. >> > Do you know the driver well enough to explain to me how the schedu= ling > inside a graphics device works? I've never seen a description of the > algorithm(s) anywhere. >=20 >=20 > Scott Bennett, Comm. ASMELG, CFIAG > ********************************************************************** > * Internet: bennett at sdf.org *xor* bennett at freeshell.org * > *--------------------------------------------------------------------* > * "A well regulated and disciplined militia, is at all times a good * > * objection to the introduction of that bane of all free governments * > * -- a standing army." * > * -- Gov. John Hancock, New York Journal, 28 January 1790 * > ********************************************************************** >=20 --=20 Arto Pekkanen --R4LCgSUlS2Fikn15sGD71OPlhB8X8521n-- --q1JrxXAiG6eEwGgOMeoKjDkJqmQ7kkU5l Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlmpf8wACgkQTBivhqtJa25zlQEAogDMGr7Jhnn39pgttK1KgWdG GO8ghH0Wr1eE2WIDft0A/0siQf8ILUfw9ug2yJI+4NVsPriO159bAX/vudqqHv3M =/roV -----END PGP SIGNATURE----- --q1JrxXAiG6eEwGgOMeoKjDkJqmQ7kkU5l--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?88a65451-d2ba-589d-20e0-9ff763ce9052>