Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 18 Sep 2002 11:32:24 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 18 Sep 2002 11:32:24 -0400 Received: from hq.fsmlabs.com ([209.155.42.197]:63447 "EHLO hq.fsmlabs.com") by vger.kernel.org with ESMTP id ; Wed, 18 Sep 2002 11:32:23 -0400 From: Cort Dougan Date: Wed, 18 Sep 2002 09:35:24 -0600 To: Ingo Molnar Cc: William Lee Irwin III , Andries Brouwer , Linus Torvalds , linux-kernel@vger.kernel.org Subject: Re: [patch] lockless, scalable get_pid(), for_each_process() elimination, 2.5.35-BK Message-ID: <20020918093523.I14918@host110.fsmlabs.com> References: <20020918090104.E14918@host110.fsmlabs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from mingo@elte.hu on Wed, Sep 18, 2002 at 05:33:54PM +0200 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1556 Lines: 32 } of course, and it should also be massively-threaded, LSB-compliant, } enterprise-ready, secure, cluster-aware, power-saving and self-healing. I } admit that there's still lots of work to be done, but there's just so many } hours in a day. get_pid() is simple, I don't see why it's taking you so long to add those features. I'll sketch out a plan for an improvement in getpid_MARK02(c) numbers once you have the prototype done. } actually, on-the-fly O(log(N)) multiprocessor garbage collection is } already integrated into its high-end modular OO design. } } > Perhaps a get_pid() that solves the Turning Halting Problem should be on } > the todo list for 2.6. Given my misspelling of Turing, I think it's clear that get_pid() needs a spellchecker. This would be an opportunity to begin work on get_pid .NET. } the first small mystery to solve are certain perturbations in Alan } Turing's name. But, yes, it's definitely a goal of the PID allocator to be } an answer to all, but also for it to avoid infinite loops for every } possible input value, while yielding slightly more subtle output than the } numeric value of 42. Patch in a few minutes. Please be sure to implement a BK replacement, open-source it, switch the kernel over to it and supply the patch in that format. It would be appreciated. - 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/