[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180730180520.GL1206094@devbig004.ftw2.facebook.com>
Date: Mon, 30 Jul 2018 11:05:20 -0700
From: Tejun Heo <tj@...nel.org>
To: Randy Dunlap <rdunlap@...radead.org>
Cc: Pavel Machek <pavel@....cz>, Johannes Weiner <hannes@...xchg.org>,
Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Suren Baghdasaryan <surenb@...gle.com>,
Vinayak Menon <vinmenon@...eaurora.org>,
Christopher Lameter <cl@...ux.com>,
Mike Galbraith <efault@....de>,
Shakeel Butt <shakeelb@...gle.com>, linux-mm@...ck.org,
cgroups@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel-team@...com
Subject: Re: [PATCH 0/10] psi: pressure stall information for CPU, memory,
and IO v2
Hello,
On Mon, Jul 30, 2018 at 10:54:05AM -0700, Randy Dunlap wrote:
> I'd say he's trying to make something that is readable and easier to
> understand for users.
Sure, it's perfectly fine to make those suggestions and discuss but
the counter points have already been discussed (e.g. PSI is a known
acronym associated with pressure and internal symbols all use them for
brevity and uniqueness). There's no clear technically winning choice
here and it's a decision of a relatively low importance given that
it's confined to kernel config. I can't see any merit in turning it
into a last-word match.
Thanks.
--
tejun
Powered by blists - more mailing lists