From: Chris Wilson <chris@chris-wilson.co.uk>
To: Paul Menzel <paulepanter@users.sourceforge.net>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Seperate fence pin counting from normal bind pin counting
Date: Sat, 09 Jul 2011 11:32:01 +0100 [thread overview]
Message-ID: <aefc95$obpb7@orsmga001.jf.intel.com> (raw)
In-Reply-To: <1310206982.4123.98.camel@mattotaupa>
[-- Attachment #1: Type: text/plain, Size: 882 bytes --]
On Sat, 09 Jul 2011 12:23:02 +0200, Paul Menzel <paulepanter@users.sourceforge.net> wrote:
> Am Samstag, den 09.07.2011, 09:25 +0100 schrieb Chris Wilson:
>
> Whoever pushes this, please correct
>
> s/Seperate/Separate/
>
> in the commit summary.
Yes, I forgot to fix the typo again.
>
> > In order to correctly account for reserving space in the GTT and fences
> > for a batch buffer, we need to independently track whether the fence is
> > pinned due to a fenced GPU access in the batch from from whether the
> > buffer is pinned in the aperture. Currently we count the fenced as
>
> »the fenced« sounds strange. Probably I need to read up the code to
> grasp that. Or is the »d« at the end a typo?
I was probably thinking of a fenced bo at the time, but the sentence reads
correctly with s/fenced/fence/.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
[-- 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:[~2011-07-09 10:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-09 8:25 [PATCH] drm/i915: Seperate fence pin counting from normal bind pin counting Chris Wilson
2011-07-09 10:23 ` Paul Menzel
2011-07-09 10:32 ` Chris Wilson [this message]
2011-11-23 10:49 ` Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2011-06-04 8:55 Chris Wilson
2011-06-04 17:38 ` Keith Packard
2011-06-04 18:31 ` Chris Wilson
2011-06-05 1:07 ` Keith Packard
2011-06-04 22:18 ` Chris Wilson
2011-06-05 20:55 ` Daniel Vetter
2011-11-13 11:00 ` Chris Wilson
2011-11-13 11:21 ` Paul Menzel
2011-11-23 12:38 ` Daniel Vetter
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='aefc95$obpb7@orsmga001.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulepanter@users.sourceforge.net \
/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