mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: Andy Lutomirski <luto@amacapital.net>
Cc: David Herrmann <dh.herrmann@gmail.com>,
	linux-api@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	systemd Mailing List <systemd-devel@lists.freedesktop.org>,
	criu@openvz.org, Pavel Emelyanov <xemul@parallels.com>,
	Cyrill Gorcunov <gorcunov@openvz.org>
Subject: Re: [RFC PATCH] proc, pidns: Add highpid
Date: Sun, 30 Nov 2014 09:47:50 +0100	[thread overview]
Message-ID: <87k32d13d5.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <b0f6c4df0e8ef8afcc7b786edecb4be8c752941e.1417215468.git.luto@amacapital.net> (Andy Lutomirski's message of "Fri, 28 Nov 2014 15:05:01 -0800")

* 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?

  parent reply	other threads:[~2014-11-30  9:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-28 23:05 Andy Lutomirski
2014-11-28 23:06 ` Andy Lutomirski
2014-11-29  3:34 ` Eric W. Biederman
2014-11-29 15:32   ` Andy Lutomirski
2014-11-29  4:23 ` Greg KH
2014-11-29 15:19   ` Andy Lutomirski
2014-11-29 16:06 ` Cyrill Gorcunov
2014-11-30  8:47 ` Florian Weimer [this message]
2014-11-30 22:08   ` Andy Lutomirski
2014-12-01  6:47     ` Florian Weimer
2014-12-01 12:33       ` Pavel Emelyanov
2014-11-30 16:45 ` David Herrmann
2014-11-30 22:05   ` Andy Lutomirski
2014-12-01  7:03 ` Konstantin Khlebnikov
2014-12-01 16:21   ` Andy Lutomirski
2014-12-01 16:39     ` Konstantin Khlebnikov
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=87k32d13d5.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=akpm@linux-foundation.org \
    --cc=criu@openvz.org \
    --cc=dh.herrmann@gmail.com \
    --cc=ebiederm@xmission.com \
    --cc=gorcunov@openvz.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=systemd-devel@lists.freedesktop.org \
    --cc=xemul@parallels.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
Powered by JetHome