From: Daniel Colascione <dancol@google.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Davidlohr Bueso <dave@stgolabs.net>,
longman@redhat.com, linux-fsdevel@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Davidlohr Bueso <dbueso@suse.de>
Subject: Re: [PATCH] fs/proc: introduce /proc/stat2 file
Date: Wed, 7 Nov 2018 16:01:20 +0000 [thread overview]
Message-ID: <CAKOZuesWpDJqqtyMxpVWBhe0ZnS3e=NOm6ZOeizuxX37tk2BbA@mail.gmail.com> (raw)
In-Reply-To: <CAJfpegvs4hafbe9XSgU175+26_ks9oh6iUo5m2tYLA=6MMvMrQ@mail.gmail.com>
On Wed, Nov 7, 2018 at 3:54 PM, Miklos Szeredi <miklos@szeredi.hu> wrote:
> On Wed, Nov 7, 2018 at 4:42 PM, Daniel Colascione <dancol@google.com> wrote:
>
>> configuration!" is something I've heard more than once. Who's to say
>> that sysfs is for exposing /proc/pid/stat,
>
> Patch is about /proc/stat not /proc/PID/stat. Please revise your
> arguments based on that.
My argument stands. The considerations I'm discussing apply to both
process-specific and system-global information files.
next prev parent reply other threads:[~2018-11-08 1:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 19:25 [PATCH] fs/proc: introduce /proc/stat2 file Davidlohr Bueso
2018-10-29 19:35 ` Waiman Long
2018-10-29 20:00 ` Davidlohr Bueso
2018-10-29 20:29 ` Waiman Long
2018-10-29 20:38 ` Davidlohr Bueso
2018-10-29 20:59 ` Waiman Long
2018-10-29 21:23 ` Vito Caputo
2018-10-29 21:35 ` Waiman Long
2018-10-29 22:41 ` Vito Caputo
2018-10-30 18:57 ` Davidlohr Bueso
2018-10-30 22:40 ` Vito Caputo
2018-10-30 23:15 ` Davidlohr Bueso
2018-10-29 21:01 ` Waiman Long
2018-10-29 23:04 ` Daniel Colascione
2018-10-30 0:58 ` Vito Caputo
2018-11-06 23:48 ` Andrew Morton
2018-11-07 3:32 ` Davidlohr Bueso
2018-11-07 16:31 ` Waiman Long
2018-11-07 10:03 ` Miklos Szeredi
2018-11-07 15:42 ` Daniel Colascione
2018-11-07 15:54 ` Miklos Szeredi
2018-11-07 16:01 ` Daniel Colascione [this message]
2018-11-07 20:32 ` Vito Caputo
2018-11-08 2:07 ` Dave Chinner
2018-11-08 7:24 ` Davidlohr Bueso
2018-11-08 7:44 ` Davidlohr Bueso
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='CAKOZuesWpDJqqtyMxpVWBhe0ZnS3e=NOm6ZOeizuxX37tk2BbA@mail.gmail.com' \
--to=dancol@google.com \
--cc=akpm@linux-foundation.org \
--cc=dave@stgolabs.net \
--cc=dbueso@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=miklos@szeredi.hu \
/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).