From: Florian Weimer <fw-d32yF4oPJVt0XxTmqZlbVQ@public.gmane.org>
To: Andy Lutomirski <luto-kltTT9wpgjJwATOyAt5JVQ@public.gmane.org>
Cc: Pavel Emelyanov <xemul-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>,
criu-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org,
Cyrill Gorcunov
<gorcunov-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>,
Andrew Morton
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
"Eric W. Biederman"
<ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>,
David Herrmann
<dh.herrmann-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
systemd Mailing List
<systemd-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
Linux API <linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-kernel@vger.kernel.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [RFC PATCH] proc, pidns: Add highpid
Date: Mon, 01 Dec 2014 07:47:26 +0100 [thread overview]
Message-ID: <87egsjrhmp.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <CALCETrV_aArOr7v4AqLHdyGGNU-5XBPmvBXEqbVU36EJ_G26uQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> (Andy Lutomirski's message of "Sun, 30 Nov 2014 14:08:13 -0800")
* Andy Lutomirski:
> On Nov 30, 2014 1:47 AM, "Florian Weimer" <fw-d32yF4oPJVt0XxTmqZlbVQ@public.gmane.org> wrote:
>>
>> * Andy Lutomirski:
>>
>> > The initial implementation is straightforward: highpid is simply a
>> > 64-bit counter. If a high-end system can fork every 3 ns (which
>> > would be amazing, given that just allocating a pid requires at
>> > atomic operation), it would take well over 1000 years for highpid to
>> > wrap.
>>
>> I'm not sure if I'm reading the patch correctly, but is the counter
>> namespaced? If yes, why?
>
> It's namespaced so that CRIU can migrate/restore a whole pid namespace.
Oh well, this requirement is at odds with system-wide uniqueness. Is
CRIU really that important? :-)
WARNING: multiple messages have this Message-ID (diff)
From: Florian Weimer <fw@deneb.enyo.de>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Pavel Emelyanov <xemul@parallels.com>,
criu@openvz.org, Cyrill Gorcunov <gorcunov@openvz.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
David Herrmann <dh.herrmann@gmail.com>,
systemd Mailing List <systemd-devel@lists.freedesktop.org>,
Linux API <linux-api@vger.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] proc, pidns: Add highpid
Date: Mon, 01 Dec 2014 07:47:26 +0100 [thread overview]
Message-ID: <87egsjrhmp.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <CALCETrV_aArOr7v4AqLHdyGGNU-5XBPmvBXEqbVU36EJ_G26uQ@mail.gmail.com> (Andy Lutomirski's message of "Sun, 30 Nov 2014 14:08:13 -0800")
* Andy Lutomirski:
> On Nov 30, 2014 1:47 AM, "Florian Weimer" <fw@deneb.enyo.de> wrote:
>>
>> * Andy Lutomirski:
>>
>> > The initial implementation is straightforward: highpid is simply a
>> > 64-bit counter. If a high-end system can fork every 3 ns (which
>> > would be amazing, given that just allocating a pid requires at
>> > atomic operation), it would take well over 1000 years for highpid to
>> > wrap.
>>
>> I'm not sure if I'm reading the patch correctly, but is the counter
>> namespaced? If yes, why?
>
> It's namespaced so that CRIU can migrate/restore a whole pid namespace.
Oh well, this requirement is at odds with system-wide uniqueness. Is
CRIU really that important? :-)
next prev parent reply other threads:[~2014-12-01 6:47 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 23:05 [RFC PATCH] proc, pidns: Add highpid Andy Lutomirski
2014-11-28 23:05 ` Andy Lutomirski
2014-11-28 23:06 ` Andy Lutomirski
2014-11-28 23:06 ` Andy Lutomirski
2014-11-30 16:45 ` David Herrmann
2014-11-30 16:45 ` David Herrmann
2014-11-30 22:05 ` Andy Lutomirski
2014-11-30 22:05 ` Andy Lutomirski
[not found] ` <b0f6c4df0e8ef8afcc7b786edecb4be8c752941e.1417215468.git.luto-kltTT9wpgjJwATOyAt5JVQ@public.gmane.org>
2014-11-29 3:34 ` Eric W. Biederman
2014-11-29 3:34 ` Eric W. Biederman
2014-11-29 15:32 ` Andy Lutomirski
2014-11-29 15:32 ` Andy Lutomirski
2014-11-29 4:23 ` Greg KH
2014-11-29 4:23 ` Greg KH
2014-11-29 15:19 ` Andy Lutomirski
2014-11-29 15:19 ` Andy Lutomirski
2014-11-29 16:06 ` Cyrill Gorcunov
2014-11-29 16:06 ` Cyrill Gorcunov
2014-11-30 8:47 ` Florian Weimer
2014-11-30 8:47 ` Florian Weimer
2014-11-30 22:08 ` Andy Lutomirski
2014-11-30 22:08 ` Andy Lutomirski
[not found] ` <CALCETrV_aArOr7v4AqLHdyGGNU-5XBPmvBXEqbVU36EJ_G26uQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-01 6:47 ` Florian Weimer [this message]
2014-12-01 6:47 ` Florian Weimer
2014-12-01 12:33 ` Pavel Emelyanov
2014-12-01 12:33 ` Pavel Emelyanov
2014-12-01 7:03 ` Konstantin Khlebnikov
2014-12-01 7:03 ` Konstantin Khlebnikov
2014-12-01 16:21 ` Andy Lutomirski
2014-12-01 16:21 ` Andy Lutomirski
[not found] ` <CALCETrW0Kmi+bJSSegjD4pSZoYhDMyQUJALZY72r388giV+ruQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-01 16:39 ` Konstantin Khlebnikov
2014-12-01 16:39 ` Konstantin Khlebnikov
2014-12-01 16:48 ` Andy Lutomirski
2014-12-01 16:48 ` 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=87egsjrhmp.fsf@mid.deneb.enyo.de \
--to=fw-d32yf4opjvt0xxtmqzlbvq@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=criu-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org \
--cc=dh.herrmann-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org \
--cc=gorcunov-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=luto-kltTT9wpgjJwATOyAt5JVQ@public.gmane.org \
--cc=systemd-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=xemul-bzQdu9zFT3WakBO8gow8eQ@public.gmane.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 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.