From owner-freebsd-current Tue May 29 10: 1:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id A32DA37B423; Tue, 29 May 2001 10:01:26 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id NAA96866; Tue, 29 May 2001 13:01:24 -0400 (EDT) (envelope-from wollman) Date: Tue, 29 May 2001 13:01:24 -0400 (EDT) From: Garrett Wollman Message-Id: <200105291701.NAA96866@khavrinen.lcs.mit.edu> To: John Cc: Current List Subject: Correctness of UIO_MAXIOV definition? In-Reply-To: <20010526205509.A14824@FreeBSD.org> References: <20010526205509.A14824@FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG < said: > The second question I have is more standards based. > Should we consider changing UIO_MAXIOV to IOV_MAX or > _XOPEN_IOV_MAX and deprecating the 1st? I am unclear > on what the standard is for this. UIO_MAXIOV is what the kernel is willing to do. IOV_MAX being standardized is what should be used by user code. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message