Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752571AbaK3WIh (ORCPT ); Sun, 30 Nov 2014 17:08:37 -0500 Received: from mail-lb0-f177.google.com ([209.85.217.177]:42457 "EHLO mail-lb0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752172AbaK3WIg (ORCPT ); Sun, 30 Nov 2014 17:08:36 -0500 MIME-Version: 1.0 In-Reply-To: <87k32d13d5.fsf@mid.deneb.enyo.de> References: <87k32d13d5.fsf@mid.deneb.enyo.de> From: Andy Lutomirski Date: Sun, 30 Nov 2014 14:08:13 -0800 Message-ID: Subject: Re: [RFC PATCH] proc, pidns: Add highpid To: Florian Weimer Cc: Pavel Emelyanov , criu@openvz.org, Cyrill Gorcunov , Andrew Morton , "Eric W. Biederman" , David Herrmann , systemd Mailing List , Linux API , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Nov 30, 2014 1:47 AM, "Florian Weimer" 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. --Andy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/