ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: Andrei Vagin <avagin@virtuozzo.com>
Cc: Kirill Kolyshkin <kir@openvz.org>,
	David Ahern <dsahern@gmail.com>,
	ksummit-discuss@lists.linuxfoundation.org,
	Patrick McHardy <kaber@trash.net>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Netlink engine issues, and ways to fix those
Date: Tue, 11 Oct 2016 17:14:16 +0300	[thread overview]
Message-ID: <CACVxJT_muz8vgu4dJ2Gk4NGjRkMgNqyJy+-bUZjk4eLnkJz6dw@mail.gmail.com> (raw)
In-Reply-To: <20161011021317.GA22492@outlook.office365.com>

>> > On Tue, Sep 13, 2016 at 12:29:35PM -0500, Eric W. Biederman wrote:

>> To some extent it matters where the cost is.
>>
>> At a practical level we already have a binary protocol for getting a
>> list of all of the processes in the system, readdir on /proc.

readdir() on /proc is only partially binary, because the interesting part
for checkpoint purposes is in text

Generic userspace may or may not convert pid back to binary
(things like top should do it because of sorting output).

And _you_ need to filter out kernel threads.

  reply	other threads:[~2016-10-11 14:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-03  5:20 Andrei Vagin
2016-09-04 19:03 ` Andy Lutomirski
2016-09-05 19:30 ` Alexei Starovoitov
2016-09-06 16:05   ` Stephen Hemminger
2016-09-12 14:05   ` Hannes Reinecke
2016-09-13 17:29 ` Eric W. Biederman
2016-09-16  5:58   ` Andrei Vagin
2016-09-18 20:18     ` Eric W. Biederman
2016-10-11  2:13       ` Andrei Vagin
2016-10-11 14:14         ` Alexey Dobriyan [this message]
2016-11-01  3:15 ` Andrei Vagin
2016-11-01 14:58   ` James Bottomley
2016-11-01 16:39     ` Theodore Ts'o
     [not found]       ` <CANaxB-ycZFtZW3=WasEDXgBwf3NF4C46aNwTOpKqHjuPbN5e-Q@mail.gmail.com>
2016-11-03 15:41         ` Andrey Vagin
2016-11-03 21:04 Kirill Kolyshkin

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=CACVxJT_muz8vgu4dJ2Gk4NGjRkMgNqyJy+-bUZjk4eLnkJz6dw@mail.gmail.com \
    --to=adobriyan@gmail.com \
    --cc=avagin@virtuozzo.com \
    --cc=dsahern@gmail.com \
    --cc=kaber@trash.net \
    --cc=kir@openvz.org \
    --cc=ksummit-discuss@lists.linuxfoundation.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