From owner-cvs-all@FreeBSD.ORG Wed Jun 16 16:21:46 2004 Return-Path: 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 3E01416A4CE; Wed, 16 Jun 2004 16:21:46 +0000 (GMT) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [128.30.28.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAFF843D2F; Wed, 16 Jun 2004 16:21:45 +0000 (GMT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: from khavrinen.lcs.mit.edu (localhost [IPv6:::1]) by khavrinen.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id i5GFhYkP009880 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK CN=khavrinen.lcs.mit.edu issuer=SSL+20Client+20CA); Wed, 16 Jun 2004 11:43:35 -0400 (EDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.12.9/8.12.9/Submit) id i5GFhYq7009877; Wed, 16 Jun 2004 11:43:34 -0400 (EDT) (envelope-from wollman) Date: Wed, 16 Jun 2004 11:43:34 -0400 (EDT) From: Garrett Wollman Message-Id: <200406161543.i5GFhYq7009877@khavrinen.lcs.mit.edu> To: Ruslan Ermilov In-Reply-To: <20040616062409.GC20866@ip.net.ua> References: <200406150124.i5F1Ofp9084012@repoman.freebsd.org> <200406151522.i5FFMeIc001885@khavrinen.lcs.mit.edu> <20040616062409.GC20866@ip.net.ua> X-Spam-Score: -9.9 () IN_REP_TO,REFERENCES X-Scanned-By: MIMEDefang 2.37 cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/lib/libc/sys read.2 X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jun 2004 16:21:46 -0000 < said: >> [I wrote:] >> Actually, it's {IOV_MAX}. > You mean you want it marked up like in POSIX, with curlies? I don't care that much about how it is marked up. The important point is that it is a configuration variable, not a constant. POSIX makes no guarantee: - that IOV_MAX will be defined as a preprocessor macro, - that sysconf(_SC_IOV_MAX) is time-invariant, or - that implementations will have any maximum at all. I have argued for a long time that such system parameters are due special markup. POSIX writes it {IOV_MAX}. -GAWollman