Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161158AbWBQVlF (ORCPT ); Fri, 17 Feb 2006 16:41:05 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1161157AbWBQVlE (ORCPT ); Fri, 17 Feb 2006 16:41:04 -0500 Received: from ebiederm.dsl.xmission.com ([166.70.28.69]:64946 "EHLO ebiederm.dsl.xmission.com") by vger.kernel.org with ESMTP id S1161155AbWBQVlB (ORCPT ); Fri, 17 Feb 2006 16:41:01 -0500 To: David Lang Cc: Jan Engelhardt , Jesper Juhl , "linux-os (Dick Johnson)" , Linux kernel Subject: Re: pid_t range question References: <9a8748490602091213p2e020355ue516d59b7d0b6c81@mail.gmail.com> From: ebiederm@xmission.com (Eric W. Biederman) Date: Fri, 17 Feb 2006 14:39:55 -0700 In-Reply-To: (David Lang's message of "Fri, 17 Feb 2006 13:20:36 -0800 (PST)") Message-ID: User-Agent: Gnus/5.1007 (Gnus v5.10.7) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 890 Lines: 22 David Lang writes: > I agree that the mojority of users don't hit this limit, but I've got a couple > of boxes that push it (they run out of ram before that, but more ram is on > order). > > however it sounds like switching to a 64 bit kernel will avoid this limit, so > I'll put my efforts into configuring a box to do that. That is what I would recommend. Unless you do something weird an painful like configure a kernel doing the 4G/4G split a 32bit box is going to have memory problems with more than 32K tasks. Just remember you need push up /proc/sys/kernel/pid-max to raise the default on a 64bit box. Eric - 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/