From owner-cvs-all  Sat Nov 16 18: 2:53 2002
Delivered-To: cvs-all@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 7247837B401; Sat, 16 Nov 2002 18:02:52 -0800 (PST)
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id D2A6143E42; Sat, 16 Nov 2002 18:02:51 -0800 (PST)
	(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: from khavrinen.lcs.mit.edu (localhost [IPv6:::1])
	by khavrinen.lcs.mit.edu (8.12.3/8.12.5) with ESMTP id gAH22oen099182
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK);
	Sat, 16 Nov 2002 21:02:50 -0500 (EST)
	(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
	by khavrinen.lcs.mit.edu (8.12.3/8.12.5/Submit) id gAH22oLd099179;
	Sat, 16 Nov 2002 21:02:50 -0500 (EST)
	(envelope-from wollman)
Date: Sat, 16 Nov 2002 21:02:50 -0500 (EST)
From: Garrett Wollman <wollman@lcs.mit.edu>
Message-Id: <200211170202.gAH22oLd099179@khavrinen.lcs.mit.edu>
To: Alfred Perlstein <alfred@FreeBSD.org>
Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject: Re: cvs commit: src/lib/libc/gen sysconf.c
In-Reply-To: <20021116095822.GT50692@elvis.mu.org>
References: <200211160635.gAG6ZKUX094649@repoman.freebsd.org>
	<200211160706.gAG76Z4S089556@khavrinen.lcs.mit.edu>
	<20021116095822.GT50692@elvis.mu.org>
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk
List-ID: <cvs-all.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20cvs-all>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20cvs-all>
X-Loop: FreeBSD.ORG

<<On Sat, 16 Nov 2002 01:58:22 -0800, Alfred Perlstein <alfred@FreeBSD.org> said:

> Should I set _POSIX_AIO_MAX to 1024?

You *must not* change _POSIX_AIO_MAX.  Its value is fixed in the
Standard.  (Specifically, it is the minimum permissible value of
{AIO_MAX}.)

The constant AIO_MAX should probably be left undefined, thereby
forcing applications to call sysconf(_SC_AIO_MAX) if they care -- but
in order for this to work, sysconf() has be able to get the correct
value of {AIO_MAX} from the kernel.

Rev. 1.18 to sysconf.c is simply wrong.  If the kernel is providing an
incorrect value, it's a bug in the kernel and should not be papered
over by the library.  If AIO is not supported in the kernel, these
values are meaningless anyway (and an error should probably be
reported).

-GAWollman


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message