From: John Harrison <John.C.Harrison@Intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, Intel-GFX@Lists.FreeDesktop.Org
Subject: Re: [PATCH v8 0/6] Convert requests to use struct fence
Date: Fri, 13 May 2016 11:11:49 +0100 [thread overview]
Message-ID: <5735A865.3040901@Intel.com> (raw)
In-Reply-To: <20160513074408.GJ23271@nuc-i3427.alporthouse.com>
On 13/05/2016 08:44, Chris Wilson wrote:
> On Thu, May 12, 2016 at 10:06:30PM +0100, John.C.Harrison@Intel.com wrote:
>> Added support for possible RCU usage of fence object (Review comments
>> by Maarten Lankhorst).
> You mean like
> https://cgit.freedesktop.org/~ickle/linux-2.6/commit/?h=tasklet&id=001f3468762ca49137b5658f2aa58507dbfa4a05
> ?
Except that that patch is 113/190 and is a lot more complex and with
different aims. The purpose of this small patch series is to add struct
fence support to the driver to allow external fence usage and scheduling
not to add RCU support to i915 for faster request list processing.
> -Chris
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-05-13 10:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 21:06 [PATCH v8 0/6] Convert requests to use struct fence John.C.Harrison
2016-05-12 21:06 ` [PATCH v8 1/6] drm/i915: Add per context timelines to fence object John.C.Harrison
2016-05-13 7:39 ` Chris Wilson
2016-05-13 9:16 ` John Harrison
2016-05-18 12:22 ` Maarten Lankhorst
2016-05-18 12:49 ` John Harrison
2016-05-18 13:20 ` Maarten Lankhorst
2016-05-12 21:06 ` [PATCH v8 2/6] drm/i915: Convert requests to use struct fence John.C.Harrison
2016-05-12 21:06 ` [PATCH v8 3/6] drm/i915: Removed now redundant parameter to i915_gem_request_completed() John.C.Harrison
2016-05-12 21:06 ` [PATCH v8 4/6] drm/i915: Interrupt driven fences John.C.Harrison
2016-05-13 7:27 ` Chris Wilson
2016-05-13 9:19 ` John Harrison
2016-05-19 9:47 ` Chris Wilson
2016-05-19 9:24 ` Maarten Lankhorst
2016-05-12 21:06 ` [PATCH v8 5/6] drm/i915: Updated request structure tracing John.C.Harrison
2016-05-12 21:06 ` [PATCH v8 6/6] drm/i915: Cache last IRQ seqno to reduce IRQ overhead John.C.Harrison
2016-05-13 7:41 ` Chris Wilson
2016-05-12 21:10 ` ✗ Ro.CI.BAT: failure for Convert requests to use struct fence (rev5) Patchwork
2016-05-13 7:44 ` [PATCH v8 0/6] Convert requests to use struct fence Chris Wilson
2016-05-13 10:11 ` John Harrison [this message]
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=5735A865.3040901@Intel.com \
--to=john.c.harrison@intel.com \
--cc=Intel-GFX@Lists.FreeDesktop.Org \
--cc=chris@chris-wilson.co.uk \
/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.