All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shakeel Butt <shakeelb@google.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Tim Murray <timmurray@google.com>,
	Michal Hocko <mhocko@kernel.org>,
	Vladimir Davydov <vdavydov.dev@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	cgroups@vger.kernel.org, Linux MM <linux-mm@kvack.org>,
	surenb@google.com, totte@google.com, kernel-team@android.com
Subject: Re: [RFC 0/1] add support for reclaiming priorities per mem cgroup
Date: Thu, 30 Mar 2017 09:48:55 -0700	[thread overview]
Message-ID: <CALvZod7Dr+YaYcSpUYCMAjotnU4hH=TnZWaL6mbBzLq=O3GJTA@mail.gmail.com> (raw)
In-Reply-To: <20170330155123.GA3929@cmpxchg.org>

> A more useful metric for memory pressure at this point is quantifying
> that time you spend thrashing: time the job spends in direct reclaim
> and on the flipside time the job waits for recently evicted pages to
> come back. Combined, that gives you a good measure of overhead from
> memory pressure; putting that in relation to a useful baseline of
> meaningful work done gives you a portable scale of how effictively
> your job is running.
>
> I'm working on that right now, hopefully I'll have something useful
> soon.

Johannes, is the work you are doing only about file pages or will it
equally apply to anon pages as well?

WARNING: multiple messages have this Message-ID (diff)
From: Shakeel Butt <shakeelb@google.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Tim Murray <timmurray@google.com>,
	Michal Hocko <mhocko@kernel.org>,
	Vladimir Davydov <vdavydov.dev@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	cgroups@vger.kernel.org, Linux MM <linux-mm@kvack.org>,
	surenb@google.com, totte@google.com, kernel-team@android.com
Subject: Re: [RFC 0/1] add support for reclaiming priorities per mem cgroup
Date: Thu, 30 Mar 2017 09:48:55 -0700	[thread overview]
Message-ID: <CALvZod7Dr+YaYcSpUYCMAjotnU4hH=TnZWaL6mbBzLq=O3GJTA@mail.gmail.com> (raw)
In-Reply-To: <20170330155123.GA3929@cmpxchg.org>

> A more useful metric for memory pressure at this point is quantifying
> that time you spend thrashing: time the job spends in direct reclaim
> and on the flipside time the job waits for recently evicted pages to
> come back. Combined, that gives you a good measure of overhead from
> memory pressure; putting that in relation to a useful baseline of
> meaningful work done gives you a portable scale of how effictively
> your job is running.
>
> I'm working on that right now, hopefully I'll have something useful
> soon.

Johannes, is the work you are doing only about file pages or will it
equally apply to anon pages as well?

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Shakeel Butt <shakeelb-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
To: Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>
Cc: Tim Murray <timmurray-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
	Michal Hocko <mhocko-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Vladimir Davydov
	<vdavydov.dev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Linux MM <linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org>,
	surenb-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org,
	totte-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org,
	kernel-team-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org
Subject: Re: [RFC 0/1] add support for reclaiming priorities per mem cgroup
Date: Thu, 30 Mar 2017 09:48:55 -0700	[thread overview]
Message-ID: <CALvZod7Dr+YaYcSpUYCMAjotnU4hH=TnZWaL6mbBzLq=O3GJTA@mail.gmail.com> (raw)
In-Reply-To: <20170330155123.GA3929-druUgvl0LCNAfugRpC6u6w@public.gmane.org>

> A more useful metric for memory pressure at this point is quantifying
> that time you spend thrashing: time the job spends in direct reclaim
> and on the flipside time the job waits for recently evicted pages to
> come back. Combined, that gives you a good measure of overhead from
> memory pressure; putting that in relation to a useful baseline of
> meaningful work done gives you a portable scale of how effictively
> your job is running.
>
> I'm working on that right now, hopefully I'll have something useful
> soon.

Johannes, is the work you are doing only about file pages or will it
equally apply to anon pages as well?

  reply	other threads:[~2017-03-30 16:48 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-17 23:16 [RFC 0/1] add support for reclaiming priorities per mem cgroup Tim Murray
2017-03-17 23:16 ` Tim Murray
2017-03-17 23:16 ` [RFC 1/1] mm, memcg: add prioritized reclaim Tim Murray
2017-03-17 23:16   ` Tim Murray
2017-03-20 14:41   ` vinayak menon
2017-03-20 14:41     ` vinayak menon
2017-03-20  5:59 ` [RFC 0/1] add support for reclaiming priorities per mem cgroup Minchan Kim
2017-03-20  5:59   ` Minchan Kim
2017-03-20 13:58   ` Vinayak Menon
2017-03-20 13:58     ` Vinayak Menon
2017-03-20 13:58     ` Vinayak Menon
2017-03-20 15:23     ` Johannes Weiner
2017-03-20 15:23       ` Johannes Weiner
2017-03-22 12:13       ` Vinayak Menon
2017-03-22 12:13         ` Vinayak Menon
2017-03-21 17:18   ` Tim Murray
2017-03-21 17:18     ` Tim Murray
2017-03-22  4:41     ` Minchan Kim
2017-03-22  4:41       ` Minchan Kim
2017-03-22  5:20       ` Minchan Kim
2017-03-22  5:20         ` Minchan Kim
2017-03-20  6:56 ` peter enderborg
2017-03-20  6:56   ` peter enderborg
2017-03-20  8:18 ` Kyungmin Park
2017-03-20  8:18   ` Kyungmin Park
2017-03-30  5:59 ` Minchan Kim
2017-03-30  5:59   ` Minchan Kim
2017-03-30  5:59   ` Minchan Kim
2017-03-30  7:10   ` Tim Murray
2017-03-30  7:10     ` Tim Murray
2017-03-30  7:10     ` Tim Murray
2017-03-30 15:51 ` Johannes Weiner
2017-03-30 15:51   ` Johannes Weiner
2017-03-30 16:48   ` Shakeel Butt [this message]
2017-03-30 16:48     ` Shakeel Butt
2017-03-30 16:48     ` Shakeel Butt
2017-04-13 16:03     ` Johannes Weiner
2017-04-13 16:03       ` Johannes Weiner
2017-03-30 19:40   ` Tim Murray
2017-03-30 19:40     ` Tim Murray
2017-03-30 21:54     ` Tim Murray
2017-03-30 21:54       ` Tim Murray
2017-04-13  4:30     ` Minchan Kim
2017-04-13  4:30       ` Minchan Kim
2017-04-13  4:30       ` Minchan Kim
2017-04-13 16:01       ` Johannes Weiner
2017-04-13 16:01         ` Johannes Weiner
2017-04-13 16:01         ` Johannes Weiner
2017-04-17  4:26         ` Minchan Kim
2017-04-17  4:26           ` Minchan Kim
2017-04-17  4:26           ` Minchan Kim

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='CALvZod7Dr+YaYcSpUYCMAjotnU4hH=TnZWaL6mbBzLq=O3GJTA@mail.gmail.com' \
    --to=shakeelb@google.com \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=surenb@google.com \
    --cc=timmurray@google.com \
    --cc=totte@google.com \
    --cc=vdavydov.dev@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 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.