From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Anholt Subject: Re: [PATCH] intel: non-blocking mmaps on the cheap Date: Wed, 21 Sep 2011 11:11:18 -0700 Message-ID: <8739fpbwah.fsf@eliezer.anholt.net> References: <20110920191934.GC2865@phenom.ffwll.local> <1316593153-7741-1-git-send-email-daniel.vetter@ffwll.ch> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1494331453==" Return-path: In-Reply-To: <1316593153-7741-1-git-send-email-daniel.vetter@ffwll.ch> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: intel-gfx@lists.freedesktop.org Cc: Daniel Vetter , Ben Widawsky List-Id: intel-gfx@lists.freedesktop.org --===============1494331453== Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" --=-=-= Content-Transfer-Encoding: quoted-printable On Wed, 21 Sep 2011 10:19:13 +0200, Daniel Vetter = wrote: > This adds a new mode to map gem objects in a non-blocking way. This > needs to be enabled on a per-object basis with object_enable_nonblocking. >=20 > The new kernel interface required to get the caching level/coherency > is not yet wired up. All the code to transparently choose between gtt > mappings or (if coherent) cpu mappings is already in place, though. >=20 > Cc: Eric Anholt > Cc: Ben Widawsky > Signed-off-by: Daniel Vetter > --- > Hi Eric, >=20 > Not really tested, but can you please take a quick lock and see if this is > suitable for mesa and ack the general approach? It doesn't quite look like what I want for Mesa, but close. Don't-block-I-know-what-I'm-doing is not a long-term property of a mapping for GL, it's something you say when you're getting a pointer to a piece of the existing mapping, and you may ask for normal blocking mode again later. So I'd rather see the the map/unmap track "oh, we already set to GTT and we haven't done something that would have knocked it out of there, so no need to go set to GTT again", instead of setting a flag. Also, I think you need to re-set to GTT after a CPU mapping on !llc, since clflushing is coarser granularity than GL buffer mappings (byte boundary). --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk56KMYACgkQHUdvYGzw6vff/wCfeasGUteCmwZbSB4eR4aheZij pSUAnA10HwaerNtD1PLoJ9UfYV3MBGSW =b6TD -----END PGP SIGNATURE----- --=-=-=-- --===============1494331453== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx --===============1494331453==--