From: Shakeel Butt <shakeelb@google.com>
To: Tim Chen <tim.c.chen@linux.intel.com>
Cc: Yang Shi <shy828301@gmail.com>,
lsf-pc@lists.linux-foundation.org, Linux MM <linux-mm@kvack.org>,
Michal Hocko <mhocko@suse.com>,
Dan Williams <dan.j.williams@intel.com>,
Dave Hansen <dave.hansen@intel.com>,
David Rientjes <rientjes@google.com>,
Wei Xu <weixugc@google.com>, Greg Thelen <gthelen@google.com>
Subject: Re: [LSF/MM TOPIC] Tiered memory accounting and management
Date: Fri, 18 Jun 2021 18:17:46 -0700 [thread overview]
Message-ID: <CALvZod70Z88fxxA7__1Yjrd=aSiKBv=pSP-W1A3DF=-xHk3PXQ@mail.gmail.com> (raw)
In-Reply-To: <f12cce6b-946b-94a7-09b4-987c92debad5@linux.intel.com>
On Fri, Jun 18, 2021 at 5:56 PM Tim Chen <tim.c.chen@linux.intel.com> wrote:
>
[...]
> >>
> >> If I understand what you are saying is you desire the kernel to provide
> >> the interface to expose performance information like
> >> "X% of accesses of high priority jobs is from high tier",
> >
> > I think we can estimate "X% of accesses to high tier" using existing
> > perf/PMU counters. So, no new interface.
>
> Using a perf counter will be okay to do for user space daemon, but I
> think there will be objections from people that the kernel
> take away a perf counter to collect perf data in kernel.
>
This is one possible policy. I would not focus too much on it unless
someone says they want exactly that. In that case we can brainstorm
how to provide general infrastructure to enforce such policies.
Basically this is like an SLO and the violation triggers the balancing
(which can be in use space or kernel and a separate discussion).
next prev parent reply other threads:[~2021-06-19 1:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 21:51 [LSF/MM TOPIC] Tiered memory accounting and management Tim Chen
2021-06-16 0:17 ` Yang Shi
2021-06-17 18:48 ` Shakeel Butt
2021-06-18 22:11 ` Tim Chen
2021-06-18 23:59 ` Shakeel Butt
2021-06-19 0:56 ` Tim Chen
2021-06-19 1:17 ` Shakeel Butt [this message]
2021-06-21 20:42 ` Yang Shi
2021-06-21 21:23 ` Shakeel Butt
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='CALvZod70Z88fxxA7__1Yjrd=aSiKBv=pSP-W1A3DF=-xHk3PXQ@mail.gmail.com' \
--to=shakeelb@google.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=gthelen@google.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mhocko@suse.com \
--cc=rientjes@google.com \
--cc=shy828301@gmail.com \
--cc=tim.c.chen@linux.intel.com \
--cc=weixugc@google.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.