Date: Mon, 20 Jul 2015 13:29:24 +0200 From: Ed Schouten <ed@nuxi.nl> To: Jilles Tjoelker <jilles@stack.nl> Cc: Ed Schouten <ed@freebsd.org>, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r285539 - head/sys/compat/cloudabi64 Message-ID: <CABh_MKmjek_KtZGitMjjNtXrqs2ioUhs=yMXKmbjKcUenSwo-w@mail.gmail.com> In-Reply-To: <20150717114153.GA93168@stack.nl> References: <201507141433.t6EEXLkn035058@repo.freebsd.org> <20150717114153.GA93168@stack.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Jilles, 2015-07-17 13:41 GMT+02:00 Jilles Tjoelker <jilles@stack.nl>: > The maximum number of iovecs is part of the ABI and should therefore > probably have a CLOUDABI_* constant. > > It turns out that both FreeBSD and Linux report 1024 for getconf > IOV_MAX, so there is little practical effect. That's a good observation. What cloudlibc does is that it leaves IOV_MAX undefined, as there is no compile-time maximum. It is therefore perfectly legal to use UIO_MAXIOV in this specific piece of code, as long as it is consistent with sysconf(_SC_IOV_MAX). If my interpretation of POSIX is correct, this should be allowed. Many of the definitions in <limits.h> may be omitted if the actual limit is unspecified. Best regards, -- Ed Schouten <ed@nuxi.nl> Nuxi, 's-Hertogenbosch, the Netherlands KvK/VAT number: 62051717
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CABh_MKmjek_KtZGitMjjNtXrqs2ioUhs=yMXKmbjKcUenSwo-w>