How the Windows Subsystem for Linux Redirects Syscalls

Re:How the Windows Subsystem for Linux Redirects Syscalls by ckaygusu on Wednesday June 08, 2016 @05:15PM (#11865730)

I think the problem here is not a syscall taking 11 parameters, it's a syscall that merely lists what is inside a directory taking 11 parameters. ataylor_284 explained the reasons (how convincingly, I'd argue) but on the first sight that surely smells bloat.

I'd also object NT kernel being more "powerful". Sure unixy kernels and NT has their differences but I don't think either one is superior.

[ Parent | on HN ]

Re:How the Windows Subsystem for Linux Redirects Syscalls by bigger_cheese on Wednesday June 08, 2016 @08:26PM (#11866779)

11 parameters may seem bloated but in some cases Unix syscalls weren't designed with enough parameters whcih caused a bunch of pain necessitating things like

dup->dup2->dup3 pipe->piep2 rename->renameat->renameat2

Best practice nowadays in linux is to allow overloading syscalls via a flags parameter.

see https://lwn.net/Articles/585415/

So modern linux syscalls may be bloated too.

[ Parent | on HN ]

Re:How the Windows Subsystem for Linux Redirects Syscalls by rbanffy on Wednesday June 08, 2016 @07:50PM (#11866620)

I remember the struct I had to populate to start a new process in 1997 or 1998...

[ Parent | on HN ]