From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915: Remove fence pipelining infrastructure
Date: Fri, 23 Mar 2012 20:13:47 +0000 [thread overview]
Message-ID: <f80fcd$3uce25@fmsmga001.fm.intel.com> (raw)
In-Reply-To: <d08817$3ksija@azsmga001.ch.intel.com>
On Fri, 23 Mar 2012 20:02:05 +0000, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Fri, 23 Mar 2012 20:18:37 +0100, Daniel Vetter <daniel@ffwll.ch> wrote:
> > Mea culpa, but I agree that it's better to reap this instead of letting it
> > languish even longer as some dead code. For the patch itself, this does
> > way too much. Imo the gem_write_fence rework and the reaping of the
> > pipelining logic should be separate patches (maybe even more) - I don't
> > quite see through this patch and follow where things move to.
>
> I got bored of rewriting the same 200 lines with the incremental churn.
> Every patch only made sense as "preparing to rip out pipelining".
Meant to add: but since it is you, I'll give it another shot.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-03-23 20:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 15:10 [PATCH 1/2] drm/i915: Reorganise rules for get_fence/put_fence Chris Wilson
2012-03-22 15:10 ` [PATCH 2/2] drm/i915: Remove fence pipelining infrastructure Chris Wilson
2012-03-23 19:18 ` Daniel Vetter
2012-03-23 20:02 ` Chris Wilson
2012-03-23 20:13 ` Chris Wilson [this message]
2012-03-23 19:08 ` [PATCH 1/2] drm/i915: Reorganise rules for get_fence/put_fence Daniel Vetter
2012-04-10 10:02 ` 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='f80fcd$3uce25@fmsmga001.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=daniel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox