From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Actually make per-fd contexts useful
Date: Wed, 21 Jan 2015 15:13:00 +0200 [thread overview]
Message-ID: <87a91c9t0i.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20150121111521.GH18602@nuc-i3427.alporthouse.com>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> On Wed, Jan 21, 2015 at 12:11:11PM +0100, Daniel Vetter wrote:
>> This goes back to when there was just one global context, when
>> restoring kinda didn't make sense.
>>
>> Also with execlist we already have these semantics, so better to be a
>> bit more consistent.
>
> Where are the benchmark results? The context switch has angered QA
> before...
>
What if we isolate fds and context by default but then let clients
choose, by using per-context parameter, if they are ok with leftover
state. From other context owned by them, or optionally even from
other clients.
- Mika
> Do we even have an igt context switch microbenchmark?
> -Chris
>
> --
> Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-01-21 13:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 11:11 [PATCH] drm/i915: Actually make per-fd contexts useful Daniel Vetter
2015-01-21 11:15 ` Chris Wilson
2015-01-21 13:13 ` Mika Kuoppala [this message]
2015-01-21 17:28 ` Dave Gordon
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=87a91c9t0i.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--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