Microsoft has developed its own Linux: in-house software-defined networking OS

Re:Microsoft has developed its own Linux: in-house software-... by pjmlp on Friday September 18, 2015 @07:08AM (#10238476)

Windows IO completion ports and the way threads are scheduled are probably only beaten by Solaris and Aix specific APIs.

Most FOSS devs never care to learn such APIs and stay with the lowest common denominator that happens to exist in GNU/Linux and *BSD.

[ Parent | on HN ]

Re:Microsoft has developed its own Linux: in-house software-... by trentnelson on Friday September 18, 2015 @10:52AM (#10239501)

> are probably only beaten by Solaris and Aix specific APIs.

They're definitely not. AIX copied the IOCP interface almost verbatim, but missed one critical piece: associating an IOCP with a desired concurrency level. Solaris added event ports, but again, they missed the concurrency link too.

The root of the problem on UNIX is the readiness I/O model.

See https://speakerdeck.com/trent/pyparallel-how-we-removed-the-... for more info.

[ Parent | on HN ]

Re:Microsoft has developed its own Linux: in-house software-... by pjmlp on Friday September 18, 2015 @03:33PM (#10241543)

Thanks for the heads up. It's been a decade since I touched Solaris and Aix.

[ Parent | on HN ]

Re:Microsoft has developed its own Linux: in-house software-... by anon4 on Friday September 18, 2015 @08:03AM (#10238663)

Do you think this will change with the popularity of node.js and libuv? That is, people using said capabilities in a cross-platform manner more.

[ Parent | on HN ]

Re:Microsoft has developed its own Linux: in-house software-... by pjmlp on Friday September 18, 2015 @10:25AM (#10239349)

I doubt it. On the enterprise space from our customers, no one cares about them.

It is all about .NET, C++ and additionally the JVM when going outside Windows.

[ Parent | on HN ]