From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Remove temporary allocation of dma addresses when rotating
Date: Mon, 27 Feb 2017 14:52:35 +0200 [thread overview]
Message-ID: <1488199955.3324.19.camel@linux.intel.com> (raw)
In-Reply-To: <20170227102159.GG13095@nuc-i3427.alporthouse.com>
On ma, 2017-02-27 at 10:21 +0000, Chris Wilson wrote:
> On Mon, Feb 27, 2017 at 10:14:12AM +0000, Tvrtko Ursulin wrote:
> > Perhaps you could say what kind of optimisation you have in mind to
> > save me guessing? :)
>
> I was thinking you would like an inactivity timer. Or we could have a
> separate shrinker, as that's the principal cache management system.
My vote goes for merging and addressing the seen problems in the
caching logic.
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-02-27 12:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 15:10 [PATCH] drm/i915: Remove temporary allocation of dma addresses when rotating Chris Wilson
2017-02-17 18:22 ` ✓ Fi.CI.BAT: success for drm/i915: Remove temporary allocation of dma addresses when rotating (rev2) Patchwork
2017-02-21 15:01 ` [PATCH] drm/i915: Remove temporary allocation of dma addresses when rotating Joonas Lahtinen
2017-02-22 8:29 ` Tvrtko Ursulin
2017-02-22 8:44 ` Chris Wilson
2017-02-27 9:55 ` Tvrtko Ursulin
2017-02-27 10:06 ` Chris Wilson
2017-02-27 10:14 ` Tvrtko Ursulin
2017-02-27 10:21 ` Chris Wilson
2017-02-27 12:52 ` Joonas Lahtinen [this message]
2017-02-27 14:31 ` Tvrtko Ursulin
2017-11-14 18:14 ` Chris Wilson
2017-11-15 9:18 ` Tvrtko Ursulin
2017-11-15 10:03 ` Chris Wilson
-- strict thread matches above, loose matches on Subject: below --
2017-02-17 15:07 Chris Wilson
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=1488199955.3324.19.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tvrtko.ursulin@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 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.