From: Dave Hansen <dave.hansen@intel.com>
To: Michal Hocko <mhocko@kernel.org>, Kuo-Hsin Yang <vovoy@chromium.org>
Cc: 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>
Subject: Re: [PATCH v3] mm, drm/i915: mark pinned shmemfs pages as unevictable
Date: Wed, 31 Oct 2018 07:40:14 -0700 [thread overview]
Message-ID: <cc44aa53-8705-02ea-6c59-f311427d93af@intel.com> (raw)
In-Reply-To: <20181031142458.GP32673@dhcp22.suse.cz>
On 10/31/18 7:24 AM, Michal Hocko wrote:
> I am also wondering whether unevictable pages culling can be
> really visible when we do the anon LRU reclaim because the swap path is
> quite expensinve on its own.
Didn't we create the unevictable lists in the first place because
scanning alone was observed to be so expensive in some scenarios?
Or am I misunderstanding your question.
next prev parent reply other threads:[~2018-10-31 14:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 8:19 Kuo-Hsin Yang
2018-10-31 9:41 ` Chris Wilson
2018-10-31 10:42 ` Vovo Yang
2018-11-01 12:20 ` Chris Wilson
2018-10-31 14:19 ` Dave Hansen
2018-11-01 12:06 ` Vovo Yang
2018-11-01 14:30 ` Dave Hansen
2018-11-02 13:22 ` Vovo Yang
2018-11-02 14:05 ` Dave Hansen
2018-11-05 11:24 ` Kuo-Hsin Yang
2018-10-31 14:24 ` Michal Hocko
2018-10-31 14:40 ` Dave Hansen [this message]
2018-10-31 16:42 ` Michal Hocko
2018-11-01 11:28 ` Vovo Yang
2018-11-01 13:09 ` Michal Hocko
2018-11-02 12:35 ` Vovo Yang
2018-11-02 18:26 ` Michal Hocko
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=cc44aa53-8705-02ea-6c59-f311427d93af@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=chris@chris-wilson.co.uk \
--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@kernel.org \
--cc=peterz@infradead.org \
--cc=vovoy@chromium.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