From: Chris Wilson <chris@chris-wilson.co.uk>
To: Mika Kuoppala <mika.kuoppala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Discard a misplaced GGTT vma
Date: Fri, 29 May 2020 15:37:54 +0100 [thread overview]
Message-ID: <159076307407.8851.10847605038685432539@build.alporthouse.com> (raw)
In-Reply-To: <87y2pastta.fsf@gaia.fi.intel.com>
Quoting Mika Kuoppala (2020-05-29 15:24:17)
> Chris Wilson <chris@chris-wilson.co.uk> writes:
>
> > Across the many users of the GGTT vma (internal objects, mmapings,
> > display etc), we may end up with conflicting requirements for the
> > placement. Currently, we try to resolve the conflict by unbinding the
> > vma and rebinding it to match the new constraints; over time we will end
> > up with a GGTT that matches the most strict constraints over all
> > concurrent users. However, this causes a problem if the vma is currently
> > in use as we must wait until it is idle before moving it. But there is
> > no restriction on the number of views we may (apart from the limited
>
> we may...have/impose?
we may have/create/use
From the object point-of-view, there is a presumption that is a single
normal view with as many partials as required (one expects up to
obj->size/chunk_size).
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-05-29 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 13:00 [Intel-gfx] [PATCH] drm/i915: Discard a misplaced GGTT vma Chris Wilson
2020-05-29 14:11 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-05-29 14:24 ` [Intel-gfx] [PATCH] " Mika Kuoppala
2020-05-29 14:37 ` Chris Wilson [this message]
2020-05-29 16:11 ` [Intel-gfx] ✓ Fi.CI.IGT: success for " Patchwork
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=159076307407.8851.10847605038685432539@build.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kuoppala@linux.intel.com \
/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;
as well as URLs for NNTP newsgroup(s).