Date: Mon, 3 Jun 2013 23:23:33 -0600 From: Warner Losh <imp@bsdimp.com> To: Konstantin Belousov <kostikbel@gmail.com> Cc: arch@FreeBSD.org, Gleb Smirnoff <glebius@FreeBSD.org> Subject: Re: aio_mlock(2) system call Message-ID: <2D222D74-31FC-4723-BE2D-A451CA1EB297@bsdimp.com> In-Reply-To: <20130604051958.GO3047@kib.kiev.ua> References: <20130603100618.GH67170@FreeBSD.org> <20130603161255.GM3047@kib.kiev.ua> <20130603212913.GU67170@glebius.int.ru> <20130604051958.GO3047@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 3, 2013, at 11:19 PM, Konstantin Belousov wrote: > On Tue, Jun 04, 2013 at 01:29:13AM +0400, Gleb Smirnoff wrote: >> On Mon, Jun 03, 2013 at 07:12:55PM +0300, Konstantin Belousov wrote: >> K> We traditionally do not reuse the gaps in the syscall table, but = add >> K> new syscalls at the end. >>=20 >> Hmm. I did that because I wanted to be all aio_* grouped together. = Why not? > The aio_* syscalls are already split between several number sequences. >=20 > I suspect that we try to not use the holes in the syscall table as > small gratis to the third-party users. Also, there was probably an > attempt to keep NetBSD/OpenBSD/FreeBSD syscall numbers out of = conflict, > which obviously failed already. Originally it was done as a courtesy to the OtherBSDs so that we would = be able to run each other's binaries. Sadly, even this small goal was = never reached, but not due to system call numbering.... Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2D222D74-31FC-4723-BE2D-A451CA1EB297>