Date: Sat, 16 Nov 2002 21:02:50 -0500 (EST) From: Garrett Wollman <wollman@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 Message-ID: <200211170202.gAH22oLd099179@khavrinen.lcs.mit.edu> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
<<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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200211170202.gAH22oLd099179>