From owner-freebsd-current@FreeBSD.ORG Thu Sep 23 19:27:51 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9AC0316A4CF for ; Thu, 23 Sep 2004 19:27:51 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D1BE43D2D for ; Thu, 23 Sep 2004 19:27:51 +0000 (GMT) (envelope-from juhasaarinen@gmail.com) Received: by mproxy.gmail.com with SMTP id 78so839971rnk for ; Thu, 23 Sep 2004 12:27:26 -0700 (PDT) Received: by 10.38.74.50 with SMTP id w50mr5495829rna; Thu, 23 Sep 2004 12:27:19 -0700 (PDT) Received: by 10.38.73.29 with HTTP; Thu, 23 Sep 2004 12:27:18 -0700 (PDT) Message-ID: Date: Fri, 24 Sep 2004 07:27:18 +1200 From: Juha Saarinen To: "David G. Lawrence" In-Reply-To: <20040923122620.GW16205@nexus.dglawrence.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20040923122620.GW16205@nexus.dglawrence.com> cc: freebsd-current@freebsd.org Subject: Re: Could ARG_MAX be increased? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Juha Saarinen List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2004 19:27:51 -0000 On Thu, 23 Sep 2004 05:26:20 -0700, David G. Lawrence wrote: > I feel compelled to respond since you mentioned me above and since I > wrote most of the code involved... :-) > The main issue with increasing the size of ARG_MAX is that it will result > in more kernel virtual memory being reserved for temporary storage of the > args. This used to be a much larger problem when KVM was scarce, but less > of a problem now with 1GB or more of KVM. The args temporary space is > allocated out of exec_map (a submap of kernel_map), which is sized to be > about 16 * ARG_MAX. The '16' is to allow up to 16 processes to simultaneously > exec until additional execs are blocked waiting for KVM to become > available. Anyway, increasing ARG_MAX to 256K (roughly 4MB of KVM) should > be okay on most systems. Very good and thorough response there :-) Is it worth putting in a PR on this? -- Juha