From: Andrew Morton <akpm@linux-foundation.org>
To: Joel Fernandes <joel@joelfernandes.org>
Cc: linux-kernel@vger.kernel.org,
Alexey Dobriyan <adobriyan@gmail.com>,
Borislav Petkov <bp@alien8.de>,
Brendan Gregg <bgregg@netflix.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Christian Hansen <chansen3@cisco.com>,
dancol@google.com, fmayer@google.com,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
Kees Cook <keescook@chromium.org>,
kernel-team@android.com, linux-api@vger.kernel.org,
linux-doc@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, Michal Hocko <mhocko@suse.com>,
Mike Rapoport <rppt@linux.ibm.com>,
minchan@kernel.org, namhyung@google.com, paulmck@linux.ibm.com,
Robin Murphy <robin.murphy@arm.com>, Roman Gushchin <guro@fb.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
surenb@google.com, Thomas Gleixner <tglx@linutronix.de>,
tkjos@google.com, Vladimir Davydov <vdavydov.dev@gmail.com>,
Vlastimil Babka <vbabka@suse.cz>, Will Deacon <will@kernel.org>,
Brendan Gregg <brendan.d.gregg@gmail.com>
Subject: Re: [PATCH v4 1/5] mm/page_idle: Add per-pid idle page tracking using virtual indexing
Date: Wed, 7 Aug 2019 13:01:22 -0700 [thread overview]
Message-ID: <20190807130122.f148548c05ec07e7b716457e@linux-foundation.org> (raw)
In-Reply-To: <20190807100013.GC169551@google.com>
On Wed, 7 Aug 2019 06:00:13 -0400 Joel Fernandes <joel@joelfernandes.org> wrote:
> > > 8 files changed, 376 insertions(+), 45 deletions(-)
> >
> > Quite a lot of new code unconditionally added to major architectures.
> > Are we confident that everyone will want this feature?
>
> I did not follow, could you clarify more? All of this diff stat is not to
> architecture code:
My point is that the patchset adds a lot of new code with no way in
which users can opt out. Almost everyone gets a fatter kernel - how
many of those users will actually benefit from it?
If "not many" then shouldn't we be making it Kconfigurable?
Are there userspace tools which present this info to users or which
provide monitoring of some form? Do major distros ship those tools?
Do people use them? etcetera.
next prev parent reply other threads:[~2019-08-07 20:01 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 17:04 [PATCH v4 1/5] mm/page_idle: Add per-pid idle page tracking using virtual indexing Joel Fernandes (Google)
2019-08-05 17:04 ` [PATCH v4 2/5] [RFC] x86: Add support for idle bit in swap PTE Joel Fernandes (Google)
2019-08-05 17:04 ` [PATCH v4 3/5] [RFC] arm64: " Joel Fernandes (Google)
2019-08-06 8:42 ` Michal Hocko
2019-08-06 10:36 ` Joel Fernandes
2019-08-06 10:47 ` Michal Hocko
2019-08-06 11:07 ` Minchan Kim
2019-08-06 11:14 ` Michal Hocko
2019-08-06 11:26 ` Joel Fernandes
2019-08-06 11:14 ` Joel Fernandes
2019-08-06 11:57 ` Michal Hocko
2019-08-06 13:43 ` Joel Fernandes
2019-08-06 14:09 ` Michal Hocko
2019-08-06 14:47 ` Minchan Kim
2019-08-06 15:20 ` Joel Fernandes
2019-08-05 17:04 ` [PATCH v4 4/5] page_idle: Drain all LRU pagevec before idle tracking Joel Fernandes (Google)
2019-08-06 8:43 ` Michal Hocko
2019-08-06 10:45 ` Joel Fernandes
2019-08-06 10:51 ` Michal Hocko
2019-08-06 11:19 ` Joel Fernandes
2019-08-06 11:44 ` Michal Hocko
2019-08-06 13:48 ` Joel Fernandes
2019-08-05 17:04 ` [PATCH v4 5/5] doc: Update documentation for page_idle virtual address indexing Joel Fernandes (Google)
2019-08-06 8:56 ` [PATCH v4 1/5] mm/page_idle: Add per-pid idle page tracking using virtual indexing Michal Hocko
2019-08-06 10:47 ` Joel Fernandes
2019-08-06 22:19 ` Andrew Morton
2019-08-07 10:00 ` Joel Fernandes
2019-08-07 20:01 ` Andrew Morton [this message]
2019-08-07 20:44 ` Joel Fernandes
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=20190807130122.f148548c05ec07e7b716457e@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adobriyan@gmail.com \
--cc=bgregg@netflix.com \
--cc=bp@alien8.de \
--cc=brendan.d.gregg@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=chansen3@cisco.com \
--cc=corbet@lwn.net \
--cc=dancol@google.com \
--cc=fmayer@google.com \
--cc=guro@fb.com \
--cc=hpa@zytor.com \
--cc=joel@joelfernandes.org \
--cc=keescook@chromium.org \
--cc=kernel-team@android.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@google.com \
--cc=paulmck@linux.ibm.com \
--cc=robin.murphy@arm.com \
--cc=rppt@linux.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=surenb@google.com \
--cc=tglx@linutronix.de \
--cc=tkjos@google.com \
--cc=vbabka@suse.cz \
--cc=vdavydov.dev@gmail.com \
--cc=will@kernel.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;
as well as URLs for NNTP newsgroup(s).