From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Ben Widawsky <ben@bwidawsk.net>,
"Kilarski, Bernard R" <bernard.r.kilarski@intel.com>
Subject: Re: [PATCH] drm/i915: IOCTL to query the cache level of a BO.
Date: Fri, 23 Sep 2011 10:00:12 +0100 [thread overview]
Message-ID: <e0d58a$1kk695@orsmga002.jf.intel.com> (raw)
In-Reply-To: <1316734033-17228-2-git-send-email-ben@bwidawsk.net>
On Thu, 22 Sep 2011 16:27:10 -0700, Ben Widawsky <ben@bwidawsk.net> wrote:
> Querying a BO's cache level can help clients wishing to map the buffer.
> For example, an Ironlake machine could query the buffer to determine it
> should use GTT mappings, while a Sandybridge machine running the same
> code would prefer to use regular CPU mapped buffers since the cache is
> coherent.
>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> Cc: Eric Anholt <eric@anholt.net>
> Cc: "Kilarski, Bernard R" <bernard.r.kilarski@intel.com>
> Signed-off-by: Ben Widawsky <ben@bwidawsk.net>
This is indeed useful.
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-09-23 9:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 23:27 [PATCH 0/4] Nonblocking maps Ben Widawsky
2011-09-22 23:27 ` [PATCH] drm/i915: IOCTL to query the cache level of a BO Ben Widawsky
2011-09-23 8:04 ` Daniel Vetter
2011-09-23 9:00 ` Chris Wilson [this message]
2011-09-22 23:27 ` [PATCH] intel: non-blocking mmaps on the cheap Ben Widawsky
2011-09-22 23:35 ` Ben Widawsky
2011-09-23 8:52 ` Daniel Vetter
2011-10-06 20:55 ` Eric Anholt
2011-10-06 22:56 ` Ben Widawsky
2011-09-22 23:27 ` [PATCH] i965: use nonblocking maps MapRangeBuffer Ben Widawsky
2011-09-23 17:15 ` Eric Anholt
2011-09-23 18:46 ` Ben Widawsky
2011-09-23 18:56 ` [Intel-gfx] " Ben Widawsky
2011-09-23 19:21 ` Ben Widawsky
2011-09-22 23:27 ` [PATCH] gpu-tools: nonblocking map test Ben Widawsky
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='e0d58a$1kk695@orsmga002.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=ben@bwidawsk.net \
--cc=bernard.r.kilarski@intel.com \
--cc=daniel.vetter@ffwll.ch \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.