From: Yang Shi <shy828301@gmail.com>
To: Dave Hansen <dave.hansen@intel.com>
Cc: lsf-pc@lists.linux-foundation.org, Linux MM <linux-mm@kvack.org>,
Michal Hocko <mhocko@kernel.org>,
Dan Williams <dan.j.williams@intel.com>,
Mel Gorman <mgorman@techsingularity.net>,
Dave Hansen <dave.hansen@linux.intel.com>,
Yang Shi <yang.shi@linux.alibaba.com>
Subject: Re: [LSF/MM/BPF TOPIC] Memory Tiering discussion
Date: Wed, 29 Jan 2020 09:24:24 -0800 [thread overview]
Message-ID: <CAHbLzkrzARtkOzoowD-L0rNnXwYtKLjtdsT6mS-auCoYXJC92Q@mail.gmail.com> (raw)
In-Reply-To: <a2e6520f-8ba7-b000-71a9-3fa8ebae1d64@intel.com>
On Tue, Jan 28, 2020 at 4:05 PM Dave Hansen <dave.hansen@intel.com> wrote:
>
> On 1/28/20 11:50 AM, Yang Shi wrote:
> > So I would like to discuss how we should move forward, what pieces we
> > still miss, what we can combine, etc.
>
> Thanks for proposing this!
>
> In addition to what you've mentioned, I'd really like to close in on
> what folks think the first set of patches we _merge_ would look like.
> More features than what we've got in the two sets? Less?
Good point. We'd better figure out the minimal viable set.
>
> I'd also like to have to rehash a few discussions we've had inside
> Intel. For instance, migrating (demoting) a page cache page is more
That would be definitely useful.
> expensive than just discarding at reclaim time. But, it might be
> expensive to recreate that page later if we do discard it. There
> doesn't seem to be a single, obviously "right" answer.
I agree, so my patchset just deals with anonymous pages. Page cache
seems more tricky.
prev parent reply other threads:[~2020-01-29 17:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 19:50 Yang Shi
2020-01-29 0:05 ` Dave Hansen
2020-01-29 17:24 ` Yang Shi [this message]
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=CAHbLzkrzARtkOzoowD-L0rNnXwYtKLjtdsT6mS-auCoYXJC92Q@mail.gmail.com \
--to=shy828301@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=yang.shi@linux.alibaba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox