aio_mlock(2) system call

Warner Losh imp at bsdimp.com
Tue Jun 4 05:23:37 UTC 2013


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.
>> 
>> 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.
> 
> 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



More information about the freebsd-arch mailing list