From: Paul Menzel <paulepanter@users.sourceforge.net>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] intel: Add support for (possibly) unsynchronized maps.
Date: Sat, 25 Feb 2012 10:03:18 +0100 [thread overview]
Message-ID: <1330160598.3345.3.camel@mattotaupa> (raw)
In-Reply-To: <1330142003-570-1-git-send-email-eric@anholt.net>
[-- Attachment #1.1: Type: text/plain, Size: 856 bytes --]
Dear Eric,
Am Freitag, den 24.02.2012, 19:53 -0800 schrieb Eric Anholt:
[…]
> +/**
> + * Performs a mapping of the buffer object like the normal GTT
> + * mapping, but avoiding waiting for the GPU to be done reading from
s/avoiding/avoids/?
> + * or rendering to the buffer.
> + *
> + * This is used in the implementation of GL_ARB_map_buffer_range: The
> + * user asks to create a buffer, then does a mapping, fills some
> + * space, runs a drawing command, then asks to map it again without
> + * synchronizing because it guarantees that it won't write over the
> + * data that the GPU is busy using (or, more specifically, that if it
> + * does write over the data, it acknowledges that rendering is
> + * undefined).
> + */
> +
> +int drm_intel_gem_bo_map_unsynchronized(drm_intel_bo *bo)
[…]
Thanks,
Paul
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2012-02-25 9:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-25 3:53 [PATCH] intel: Add support for (possibly) unsynchronized maps Eric Anholt
2012-02-25 3:53 ` [PATCH] intel: Make use of the new GPU-unsynchronized map functionality in libdrm Eric Anholt
2012-02-25 8:55 ` [PATCH] intel: Add support for (possibly) unsynchronized maps Chris Wilson
2012-02-25 9:03 ` Paul Menzel [this message]
2012-02-25 11:00 ` Daniel Vetter
2012-02-25 11:16 ` Chris Wilson
2012-02-26 20:28 ` Kenneth Graunke
2012-02-27 11:15 ` Ben Widawsky
2012-02-27 19:05 ` Eric Anholt
2012-02-28 7:35 ` [PATCH 1/2] intel: Fix error check for I915_PARAM_HAS_LLC Eric Anholt
2012-02-28 7:35 ` [PATCH 2/2] intel: Add support for (possibly) unsynchronized maps Eric Anholt
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=1330160598.3345.3.camel@mattotaupa \
--to=paulepanter@users.sourceforge.net \
--cc=intel-gfx@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