I cannot stop thinking that soon they will announce a native implementation of Docker on top of all that.
Windows Subsystem for Linux Architectural Overview
21–30 of 43 posts
Re: Windows Subsystem for Linux Architectural Overview
#22So `fork` is still expensive?
I think I read somewhere else that they use a better implementation here. Cygwin and SUA being user-mode pieces were limited to a slow fork, but in kernel mode they can emulate things properly.
Re: Windows Subsystem for Linux Architectural Overview
#23I cannot stop thinking that soon they will announce a native implementation of Docker on top of all that.
Given they're working with docker and pretty much announced all but that, I think that that's more a guarantee than ponderance.
Re: Windows Subsystem for Linux Architectural Overview
#24I cannot stop thinking that soon they will announce a native implementation of Docker on top of all that.
They have not implemented namespaces or cgroups in the Linux emulation, so I doubt it. Docker on Windows will only run Windows binaries.
Re: Windows Subsystem for Linux Architectural Overview
#25> The primary role of SUA was to encourage applications to get ported to Windows without significant rewrites. Is this a supported use of the Linux subsystem? Running native Linux apps directly is great if it works but there are going to be cases where the app would 99% work except for that one thing Linux has and the Linux subsystem doesn't. Maybe Microsoft doesn't provide a tun/tap driver so you need to use TAP-Win…
Microsoft are insane about providing compatibility when it suits them. It will work - if they see a business case for it.
I was just thinking after reading this - sure there were some engineering marvels that enabled this, but for the implementation it was just rote work with the sheer manpower Microsoft can muster up. That in itself is just really impressive.
Edit: giving it more thought, a Mozilla engineer recently demo'd an immediate mode rendering engine that him and one other dev wrote in 9 months, with feature parity of modern browsers. So either way - big engineering effort or a couple '10x developers' - pretty impressive .
Re: Windows Subsystem for Linux Architectural Overview
#26So, its kind of LINE for Windows like WINE for Linux.
There is, or was a program called LINE doing just that.
Re: Windows Subsystem for Linux Architectural Overview
#27So `fork` is still expensive?
Does the fork performance really matter these days anymore? I mean comparing from one side to the speed of loading the app itself, fork is usually super cheap; on the other comparing to per-process async event handling, it's so slow pretty much nobody uses it this way for network apps anymore. What's the use case for a fast fork today?
Re: Windows Subsystem for Linux Architectural Overview
#28So `fork` is still expensive?
Does the fork performance really matter these days anymore? I mean comparing from one side to the speed of loading the app itself, fork is usually super cheap; on the other comparing to per-process async event handling, it's so slow pretty much nobody uses it this way for network apps anymore. What's the use case for a fast fork today?
One example: The HyPer in-memory database from TUM uses fork to provide fast snapshots for running OLAP queries on fresh data.
[1]: http://hyper-db.de
Re: Windows Subsystem for Linux Architectural Overview
#29Does this enable running Docker containers of Linux things in Windows? Would that enable an improvement on Docker's VirtualBox workaround?
Re: Windows Subsystem for Linux Architectural Overview
#30So `fork` is still expensive?
Does the fork performance really matter these days anymore? I mean comparing from one side to the speed of loading the app itself, fork is usually super cheap; on the other comparing to per-process async event handling, it's so slow pretty much nobody uses it this way for network apps anymore. What's the use case for a fast fork today?
Redis uses fork to save to disk.