From: Andy Lutomirski <luto@amacapital.net>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux API <linux-api@vger.kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Djalal Harouni <tixxdz@gmail.com>,
Alexey Gladkov <gladkov.alexey@gmail.com>,
Tatsiana Brouka <Tatsiana_Brouka@epam.com>,
Aliaksandr Patseyenak <Aliaksandr_Patseyenak1@epam.com>
Subject: Re: [PATCH v2 2/2] pidmap(2)
Date: Wed, 27 Sep 2017 08:04:26 -0700 [thread overview]
Message-ID: <CALCETrUJbVSPTpVqmHRTcELUCjAnQWVcsG7urcQgoHv13a+aOQ@mail.gmail.com> (raw)
In-Reply-To: <20170926184643.GC14724@avx2>
On Tue, Sep 26, 2017 at 11:46 AM, Alexey Dobriyan <adobriyan@gmail.com> wrote:
> On Sun, Sep 24, 2017 at 02:27:00PM -0700, Andy Lutomirski wrote:
>> On Sun, Sep 24, 2017 at 1:08 PM, Alexey Dobriyan <adobriyan@gmail.com> wrote:
>> > From: Tatsiana Brouka <Tatsiana_Brouka@epam.com>
>> >
>> > Implement system call for bulk retrieveing of pids in binary form.
>> >
>> > Using /proc is slower than necessary: 3 syscalls + another 3 for each thread +
>> > converting with atoi() + instantiating dentries and inodes.
>> >
>> > /proc may be not mounted especially in containers. Natural extension of
>> > hidepid=2 efforts is to not mount /proc at all.
>> >
>> > It could be used by programs like ps, top or CRIU. Speed increase will
>> > become more drastic once combined with bulk retrieval of process statistics.
>> >
>> > Benchmark:
>> >
>> > N=1<<16 times
>> > ~130 processes (~250 task_structs) on a regular desktop system
>> > opendir + readdir + closedir /proc + the same for every /proc/$PID/task
>> > (roughly what htop(1) does) vs pidmap
>> >
>> > /proc 16.80 ą 0.73%
>> > pidmap 0.06 ą 0.31%
>> >
>> > PIDMAP_* flags are modelled after /proc/task_diag patchset.
>> >
>> >
>> > PIDMAP(2) Linux Programmer's Manual PIDMAP(2)
>> >
>> > NAME
>> > pidmap - get allocated PIDs
>> >
>> > SYNOPSIS
>> > long pidmap(pid_t pid, int *pids, unsigned int count , unsigned int start, int flags);
>>
>> I think we will seriously regret a syscall that does this. Djalal is
>> working on fixing the turd that is hidepid, and this syscall is
>> basically incompatible with ever fixing hidepids. I think that, to
>> make it less regrettable, it needs to take an fd to a proc mount as a
>> parameter. This makes me wonder why it's a syscall at all -- why not
>> just create a new file like /proc/pids?
>
> See reply to fdmap(2).
>
> pidmap(2) is indeed more complex case exactly because of
> pid/tgid/tid/everything else + pidnamespaces + ->hide_pid.
> However the problem remains: query task tree without all the bullshit.
> C/R people succumbed with /proc/*/children, it was a mistake IMO.
Your syscall cannot be implemented sanely. It doesn't remove bullshit
-- it adds bullshit. NAK.
next prev parent reply other threads:[~2017-09-27 15:04 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-24 20:06 [PATCH 1/2 v2] fdmap(2) Alexey Dobriyan
2017-09-24 20:08 ` [PATCH v2 2/2] pidmap(2) Alexey Dobriyan
2017-09-24 21:27 ` Andy Lutomirski
[not found] ` <CALCETrWTJmfS6gBHonKFUKYMtcXuQ9XXmWRdP0aP9Mpv7J9=nw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-09-26 18:46 ` Alexey Dobriyan
2017-09-27 15:04 ` Andy Lutomirski [this message]
2017-09-25 7:43 ` Michael Kerrisk (man-pages)
2017-09-25 10:47 ` Djalal Harouni
2017-09-26 5:44 ` kbuild test robot
2017-09-24 21:31 ` [PATCH 1/2 v2] fdmap(2) Andy Lutomirski
[not found] ` <CALCETrWWUuzF7HaQAS2rf69KcqBrB9epvQPPgKEoK4MNbdVmEw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-09-26 18:43 ` Alexey Dobriyan
2017-09-25 7:42 ` Michael Kerrisk (man-pages)
[not found] ` <9bc11ace-d111-cdef-5280-8cdda027ae9a-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-09-26 19:00 ` Alexey Dobriyan
2017-09-27 15:03 ` Andy Lutomirski
[not found] ` <CALCETrWTTe2X6O5HQMWJC84yXNBJ+eERJoDZMowq8X1L0q7pEQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-09-28 7:26 ` Michael Kerrisk (man-pages)
2017-09-28 10:55 ` Alexey Dobriyan
[not found] ` <CACVxJT_B4m-O66haETWkFVx5AgGqDbM-K-53odJ0bRp0_2xhrQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-09-28 15:02 ` Andy Lutomirski
2017-10-11 17:37 ` Alexey Dobriyan
2017-09-28 10:10 ` Alexey Dobriyan
2017-10-23 9:29 ` Pavel Machek
2017-10-25 12:45 ` Alexey Dobriyan
2017-10-25 13:48 ` Pavel Machek
2017-09-26 4:25 ` kbuild test robot
2017-10-10 22:08 ` [1/2,v2] fdmap(2) Andrei Vagin
2017-10-11 18:12 ` Alexey Dobriyan
2017-10-12 8:06 ` Andrei Vagin
[not found] ` <20171012080608.GA23077-1ViLX0X+lBJGNQ1M2rI3KwRV3xvJKrda@public.gmane.org>
2017-10-18 11:35 ` Alexey Dobriyan
2017-10-18 17:47 ` Andy Lutomirski
2017-10-19 15:34 ` Alexey Dobriyan
2017-10-20 7:48 ` Greg KH
[not found] ` <20171020074829.GA9010-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2017-10-25 13:11 ` Alexey Dobriyan
[not found] ` <CACVxJT_AKQmd0ziP7jWQvfA5MQGJgC2q2VA3xyFjVARrQR-ekg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-10-26 7:53 ` Andy Lutomirski
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=CALCETrUJbVSPTpVqmHRTcELUCjAnQWVcsG7urcQgoHv13a+aOQ@mail.gmail.com \
--to=luto@amacapital.net \
--cc=Aliaksandr_Patseyenak1@epam.com \
--cc=Tatsiana_Brouka@epam.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=gladkov.alexey@gmail.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=tglx@linutronix.de \
--cc=tixxdz@gmail.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 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).