From: Alexey Dobriyan <adobriyan@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Greg KH <gregkh@linuxfoundation.org>, linux-kernel@vger.kernel.org
Subject: Re: "statsfs" API design
Date: Mon, 11 Nov 2019 23:40:32 +0300 [thread overview]
Message-ID: <20191111204032.GA14256@avx2> (raw)
In-Reply-To: <9fe3a096-20b9-979a-d4d7-48a37b059dff@redhat.com>
On Sun, Nov 10, 2019 at 09:58:14PM +0100, Paolo Bonzini wrote:
> On 10/11/19 16:34, Alexey Dobriyan wrote:
> > In the other direction: describe every field of /proc/*/stat file
> > without looking to the manpage:
> >
> > $ cat /proc/self/stat
> > 5349 (cat) R 5342 5349 5342 34826 5349 4210688 91 0 0 0 0 0 0 0 20 0 1 0 864988 9183232 184 18446744073709551615 94352028622848 94352028651936 140733810522864 0 0 0 0 0 0 0 0 0 17 5 0 0 0 0 0 94352030751824 94352030753376 94352060055552 140733810527527 140733810527547 140733810527547 140733810532335 0
>
> That's why this is not what I am proposing, and also not what Greg has
> mentioned.
The argument was that text is somehow superior to binary. Experiment shows
that userspace can make a mess of both modes therefore preferring one
to another should be based on something else (preferably objective).
/proc have these two problems:
First, noticeably slow:
https://news.ycombinator.com/item?id=21414882
Second, overinstantiating inodes and dentries:
https://lore.kernel.org/lkml/20180424022106.16952-1-jeffm@suse.com/
statfs maybe never get to that level but it is not hard to see what lies
at the end of the tunnel.
next prev parent reply other threads:[~2019-11-11 20:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-09 18:44 "statsfs" API design Alexey Dobriyan
2019-11-10 9:14 ` Greg KH
2019-11-10 10:09 ` Brian Masney
2019-11-10 10:14 ` Greg KH
2019-11-10 10:19 ` Greg KH
2019-11-10 15:34 ` Alexey Dobriyan
2019-11-10 20:58 ` Paolo Bonzini
2019-11-11 20:40 ` Alexey Dobriyan [this message]
2019-11-26 10:07 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2019-11-06 15:56 Paolo Bonzini
2019-11-09 15:49 ` Greg Kroah-Hartman
2019-11-10 13:04 ` Paolo Bonzini
2019-11-26 10:09 ` Greg Kroah-Hartman
2019-11-26 10:50 ` Paolo Bonzini
2019-11-26 14:18 ` Greg Kroah-Hartman
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=20191111204032.GA14256@avx2 \
--to=adobriyan@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.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.