From owner-freebsd-current@FreeBSD.ORG Thu Aug 16 03:06:54 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7F9116A417 for ; Thu, 16 Aug 2007 03:06:54 +0000 (UTC) (envelope-from wilkinsa@obelix.dsto.defence.gov.au) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.freebsd.org (Postfix) with ESMTP id 6F27313C469 for ; Thu, 16 Aug 2007 03:06:54 +0000 (UTC) (envelope-from wilkinsa@obelix.dsto.defence.gov.au) Received: from ednmsw510.dsto.defence.gov.au (ednmsw510.dsto.defence.gov.au [131.185.68.11]) by digger1.defence.gov.au (8.13.8/8.13.8) with ESMTP id l7G2ttZS019144 for ; Thu, 16 Aug 2007 12:25:55 +0930 (CST) Received: from ednex510.dsto.defence.gov.au (ednex510.dsto.defence.gov.au) by ednmsw510.dsto.defence.gov.au (Clearswift SMTPRS 5.2.9) with ESMTP id for ; Thu, 16 Aug 2007 12:36:45 +0930 Received: from obelix.dsto.defence.gov.au ([203.6.60.208]) by ednex510.dsto.defence.gov.au with Microsoft SMTPSVC(6.0.3790.1830); Thu, 16 Aug 2007 12:36:45 +0930 Received: from obelix.dsto.defence.gov.au (localhost [127.0.0.1]) by obelix.dsto.defence.gov.au (8.14.1/8.14.1) with ESMTP id l7G35fU7016497 for ; Thu, 16 Aug 2007 11:05:41 +0800 (WST) (envelope-from wilkinsa@obelix.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by obelix.dsto.defence.gov.au (8.14.1/8.14.1/Submit) id l7G35fe4016496 for freebsd-current@freebsd.org; Thu, 16 Aug 2007 11:05:41 +0800 (WST) (envelope-from wilkinsa) Date: Thu, 16 Aug 2007 11:05:41 +0800 From: "Wilkinson, Alex" To: freebsd-current@freebsd.org Message-ID: <20070816030540.GO11649@obelix.dsto.defence.gov.au> Mail-Followup-To: freebsd-current@freebsd.org References: <20070812114017.GA93036@obelix.dsto.defence.gov.au> <20070815104929.GJ11649@obelix.dsto.defence.gov.au> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: Organisation: Defence Science Technology Organisation User-Agent: Mutt/1.5.16 (2007-06-09) X-OriginalArrivalTime: 16 Aug 2007 03:06:45.0647 (UTC) FILETIME=[7A8B49F0:01C7DFB2] X-TM-AS-Product-Ver: SMEX-7.0.0.1526-5.0.1021-15364.000 X-TM-AS-Result: No--1.107800-0.000000-31 Content-Transfer-Encoding: 7bit Subject: Re: SEC:ULarger NGROUPS_MAX in CURRENT ? Ready for 7.0-R ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Aug 2007 03:06:55 -0000 0n Wed, Aug 15, 2007 at 10:40:07AM -0700, Doug Barton wrote: >> AFAIK the only problem with this is that NFS will fail with larger >> number of groups, so (for those not using NFS) why not make the number >> of groups an item in kernel configurations and make a compile-time and >> module-load-time checks for this in the NFS code? > >Sure, we look forward to reviewing your patches. Linux has done some interesting work with respect to this. They have implemented "Dynamic Allocation of Groups Array When Required" [http://lwn.net/Articles/50916/]. And can allocate up to: #cat /proc/sys/kernel/ngroups_max 65536 I thought NFSv4 no longer has the 16 group limitation ? -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.