From: Sean V Kelley <seanvk@posteo.de>
To: Daniel Vetter <daniel@ffwll.ch>,
Chris Wilson <chris@chris-wilson.co.uk>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
stable <stable@vger.kernel.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Do not invalidate obj->pages under mempressure
Date: Sun, 08 Feb 2015 15:27:13 -0800 [thread overview]
Message-ID: <54D7F0D1.3070803@posteo.de> (raw)
In-Reply-To: <CAKMK7uFtR+UWix6B-x81x90MeQhhtvnD+nr0auCrN_tSzyBO3Q@mail.gmail.com>
On 01/16/2015 08:05 PM, Daniel Vetter wrote:
> On Thu, Jan 15, 2015 at 08:44:00PM +0000, Chris Wilson wrote:
>> On Thu, Jan 15, 2015 at 08:36:15PM +0100, Daniel Vetter wrote:
>>> On Wed, Jan 14, 2015 at 9:34 PM, Chris Wilson
>>> <chris@chris-wilson.co.uk> wrote:
>>>> This (partially) reverts
>>>>
>>>> commit 5537252b6b6d71fb1a8ed7395a8e5babf91953fd Author: Chris
>>>> Wilson <chris@chris-wilson.co.uk> Date: Tue Mar 25 13:23:06
>>>> 2014 +0000
>>>>
>>>> drm/i915: Invalidate our pages under memory pressure
>>>
>>> Shouldn't we also revert the hunk in i915_gem_free_objects?
>>> Without the truncate vs. invalidate disdinction it seems to
>>> have lost it's reason for existence ...
>>
>> No, setting MADV_DONTNEED has other nice properties during
>> put_pages() - I think it is useful in its own right, for example
>> that is where my page stealing code goes...
>
> Well right now I can't make sense of this bit any more (tbh I
> didn't with the other code either, but overlooked that while
> reviewing). When it's just there for future work but atm dead code
> I prefer for it to get removed. -Daniel
So can we also revert the hunk in i915_gem_free_objects? I would like
to get this patch merged, it looks like that is the primary concern.
Thanks,
Sean
>
next prev parent reply other threads:[~2015-02-08 23:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 20:34 [PATCH] drm/i915: Do not invalidate obj->pages under mempressure Chris Wilson
2015-01-15 0:55 ` [Intel-gfx] " Daniel Vetter
2015-01-15 1:19 ` Sean V Kelley
2015-01-15 9:38 ` Chris Wilson
2015-01-15 2:11 ` shuang.he
2015-01-15 19:36 ` Daniel Vetter
2015-01-15 20:44 ` [Intel-gfx] " Chris Wilson
2015-01-17 4:05 ` Daniel Vetter
2015-02-08 23:27 ` Sean V Kelley [this message]
2015-02-09 16:46 ` [Intel-gfx] " Chris Wilson
2015-02-09 18:31 ` Sean V Kelley
2015-02-11 0:55 ` Sean V Kelley
2015-02-11 13:02 ` Daniel Vetter
2015-02-20 22:19 ` Sean V Kelley
2015-02-09 16:43 ` Daniel Vetter
2015-02-10 8:19 ` shuang.he
2015-02-10 11:38 ` Jani Nikula
2015-02-24 13:27 ` Jani Nikula
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=54D7F0D1.3070803@posteo.de \
--to=seanvk@posteo.de \
--cc=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stable@vger.kernel.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 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.