linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Gavin Shan <gshan@redhat.com>
To: Yang Shi <shy828301@gmail.com>
Cc: Roman Gushchin <guro@fb.com>, Linux MM <linux-mm@kvack.org>,
	drjones@redhat.com, david@redhat.com, bhe@redhat.com,
	Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [RFC PATCH] mm/vmscan: Don't round up scan size for online memory cgroup
Date: Wed, 12 Feb 2020 13:38:34 +1100	[thread overview]
Message-ID: <2c722ed4-7358-a26d-2219-2a9938b4fbf9@redhat.com> (raw)
In-Reply-To: <CAHbLzkoQHSX-5pBfYSB2Dbw95EEQjSZtGfqKyv9qvSASO1A79g@mail.gmail.com>

On 2/11/20 2:03 PM, Yang Shi wrote:
> On Mon, Feb 10, 2020 at 6:18 PM Gavin Shan <gshan@redhat.com> wrote:
>> On 2/11/20 12:31 PM, Roman Gushchin wrote:
>>> On Tue, Feb 11, 2020 at 10:55:53AM +1100, Gavin Shan wrote:
>>>> On 2/11/20 3:17 AM, Roman Gushchin wrote:
>>>>> On Mon, Feb 10, 2020 at 11:14:45PM +1100, Gavin Shan wrote:

.../...

>>
>> There is something which might be unrelated to discuss here: the pagecache could be backed
>> by a low-speed (HDD) or high-speed (SSD) media. So the cost to fetch them from disk to memory
>> isn't equal, meaning we need some kind of bias during reclaiming. It seems something missed
>> from current implementation.
> 
> Yes, the refault cost was not taken into account. I recalled Johannes
> posted a patch series to do swap with refault cost weighted in a
> couple of years ago, please see: https://lwn.net/Articles/690079/.
> 

Thanks for the link. Yes, Johannes's patchset is comprehensive, even I
didn't look into the details. The concern I had is fixed bias to pagecaches
backed by different storage device, which have different IO speed. It seems
the patchset was disconnected since v1 because I didn't find a v2 from
google.

Thanks,
Gavin



  reply	other threads:[~2020-02-12  2:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-10 12:14 Gavin Shan
2020-02-10 16:17 ` Roman Gushchin
2020-02-10 23:55   ` Gavin Shan
2020-02-11  1:31     ` Roman Gushchin
2020-02-11  2:17       ` Gavin Shan
2020-02-11  3:03         ` Yang Shi
2020-02-12  2:38           ` Gavin Shan [this message]
2020-02-11 14:42         ` Roman Gushchin

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=2c722ed4-7358-a26d-2219-2a9938b4fbf9@redhat.com \
    --to=gshan@redhat.com \
    --cc=bhe@redhat.com \
    --cc=david@redhat.com \
    --cc=drjones@redhat.com \
    --cc=guro@fb.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-mm@kvack.org \
    --cc=shy828301@gmail.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