From: Kuo-Hsin Yang <vovoy@chromium.org>
To: linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org,
linux-mm@kvack.org, Chris Wilson <chris@chris-wilson.co.uk>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Dave Hansen <dave.hansen@intel.com>,
Michal Hocko <mhocko@suse.com>
Subject: Re: [PATCH v6] mm, drm/i915: mark pinned shmemfs pages as unevictable
Date: Tue, 6 Nov 2018 23:19:12 +0800 [thread overview]
Message-ID: <CAEHM+4oLesko3TPGDm2+FTCJT=gYw4fy0YmCQGuT1CTHFZgmkg@mail.gmail.com> (raw)
In-Reply-To: <20181106105406.GO21967@phenom.ffwll.local>
On Tue, Nov 6, 2018 at 6:54 PM Daniel Vetter <daniel@ffwll.ch> wrote:
> There was ages ago some planes to have our own i915fs, so that we could
> overwrite the address_space hooks for page migration and eviction and that
> sort of thing, which would make all these pages evictable. Atm you have to
> ĥope our shrinker drops them on the floor, which I think is fairly
> confusing to core mm code (it's kinda like page eviction worked way back
> before rmaps).
>
Thanks for the explanation. Your blog posts helped a lot to get me
started on hacking drm/i915 driver.
> Just an side really.
> -Daniel
>
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> http://blog.ffwll.ch
next prev parent reply other threads:[~2018-11-06 15:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 9:30 [PATCH v6] mm, drm/i915: mark pinned shmemfs pages as unevictable Kuo-Hsin Yang
2018-11-06 10:54 ` Daniel Vetter
2018-11-06 15:19 ` Kuo-Hsin Yang [this message]
2018-11-06 11:06 ` Chris Wilson
2018-11-06 11:49 ` Kuo-Hsin Yang
2018-11-06 12:14 ` Michal Hocko
2018-11-06 13:23 ` [PATCH v7] " Chris Wilson
2018-11-06 14:14 ` Kuo-Hsin Yang
2018-11-06 17:32 ` Dave Hansen
2018-11-06 18:12 ` Andrew Morton
2018-11-07 15:34 ` 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='CAEHM+4oLesko3TPGDm2+FTCJT=gYw4fy0YmCQGuT1CTHFZgmkg@mail.gmail.com' \
--to=vovoy@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=chris@chris-wilson.co.uk \
--cc=dave.hansen@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).