9front - general discussion about 9front
 help / color / mirror / Atom feed
From: David Arnold <davida@pobox.com>
To: 9front@9front.org
Cc: David Arnold <davida@pobox.com>
Subject: Re: [9front] hackathon writeup
Date: Sat, 20 Aug 2022 07:13:20 +1000	[thread overview]
Message-ID: <C35074E3-E6AB-45BD-86E9-2824E85C3C5F@pobox.com> (raw)
In-Reply-To: <CAG3JMtZfaBaAzp-JzfDenxp7E37wTL0NU0vPKBwAs1eAb6TjDg@mail.gmail.com>

> On 20 Aug 2022, at 05:52, Thaddeus Woskowiak <tswoskowiak@gmail.com> wrote:
> 
>> The syscalls problem isn't that we don't know which ones to implement,
>> it's that Linux creates and deprecates them at a rate faster than anyone
>> can keep up with.  I am positive this is the case worldwide, not just
>> for us -- otherwise, things like Docker on OS X would not virtualize an
>> entire OS just to make use of Linux containers.  The engineering cost to
>> virtualize a platform and boot Linux on it is lower than the engineering
>> cost to keep up with whatever the hell the Linux horde throws at the
>> kernel this week.
>> 
>> khm
> 
> Indeed. Even Microsoft gave up emulating a Linux kernel in WSL and
> instead virtualize a Linux kernel in Hyper-V in WSL2.

To be fair, that was largely due to the impedance mismatch between Linux’
Unix-style syscalls and the NT kernel model causing performance problems.

That said, operating systems appear to have adapted to emulated hardware
better than applications have adapted to emulated operating systems.




d


  reply	other threads:[~2022-08-19 21:16 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-17  3:27 ori
2022-08-18 22:37 ` Stuart Morrow
2022-08-18 22:52 ` Stuart Morrow
2022-08-18 23:09   ` Stanley Lieber
2022-08-18 23:32     ` Stuart Morrow
2022-08-18 23:11   ` Kurt H Maier
2022-08-18 23:33     ` Stuart Morrow
2022-08-18 23:55       ` Jacob Moody
2022-08-19  0:05         ` ori
2022-10-14  5:45           ` 9p2000.ix (Was Re: [9front] hackathon writeup) unobe
2022-08-19 11:34         ` [9front] hackathon writeup Stuart Morrow
2022-08-19 13:21           ` Jacob Moody
2022-08-18 23:04 ` Stuart Morrow
2022-08-18 23:24   ` ori
2022-08-18 23:37     ` Stuart Morrow
2022-08-18 23:43       ` ori
2022-08-19  0:02       ` Kurt H Maier
2022-08-19  0:23         ` qwx
2022-08-19  1:54           ` Kurt H Maier
2022-08-19  2:02             ` qwx
2022-08-19  7:08         ` Steve Simon
2022-08-20  1:38           ` Xiao-Yong Jin
2022-08-20  3:57             ` ori
2022-08-19 19:52         ` Thaddeus Woskowiak
2022-08-19 21:13           ` David Arnold [this message]
2022-08-19 19:11   ` Aram Hăvărneanu
2022-08-19 20:40     ` Stuart Morrow
2022-08-20 13:14       ` Stuart Morrow
2022-08-22 17:54         ` Aram Hăvărneanu
2022-08-22 17:56           ` Kurt H Maier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C35074E3-E6AB-45BD-86E9-2824E85C3C5F@pobox.com \
    --to=davida@pobox.com \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).