From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: guix-devel@gnu.org
Subject: Re: FYI: guile-scheme bindings to GNU Mach and the Hurd
Date: Tue, 11 May 2021 22:29:53 +0200 [thread overview]
Message-ID: <87o8dhvwse.fsf@gnu.org> (raw)
In-Reply-To: <e88dcf7fe230a7e2f21c5d40a93bbab08875179a.camel@telenet.be> (Maxime Devos's message of "Thu, 06 May 2021 22:58:07 +0200")
Hi!
Maxime Devos <maximedevos@telenet.be> skribis:
> Ludovic Courtès schreef op do 06-05-2021 om 18:30 [+0200]:
>> BTW, a dream of mine was to implement RPCs in Scheme. That is, you’d
>> have a macro that would essentially do the same work as MiG (the Mach
>> Interface Generator), and then we’d pass the bytes directly to
>> ‘mach_msg’.
>
> The lisp bindings have a binding to ‘mach_msg’ (not yet schemified).
> Note that the lisp hurd bindings never use "send-message", instead they
> bind the C bindings generated by MiG.
>
> Also, ‘implementing RPCs in Scheme’ is something I would like to see
> as well.
>
> One thing I have in mind, is that MiG RPCs can block, but mach_msg
> itself seems to be perfectly usable in a non-blocking way (maybe using
> port notifications?). If we use something like guile-fibers, and integrate
> guile-hurd with fibers, then we may be able to do crazy things like:
>
> * asynchronuously opening files, for free!
> * asynchronuous 'accept', for free!
> * asynchronuous disk I/O, for free!
> * asynchronuous ... practically anything, for free!
Oh yes, it has great potential.
And it cannot be That Hard (famous last words).
Food for thought!
> Another possibility is debugging the translator responsible for IP
> and at the same time running a web browser (or IRC client, or ...)
> based on guile-fibers+guile-hurd. The web browser wouldn't be overly
> bothered by the network translator temporarily being paused (for debugging)
> and therefore not responsing to the RPCs for 'connect' et al.
>
> Loading webpages will be delayed of course, but the browser itself won't
> hang (so you can still scroll, copy & paste, perhaps browse the file system
> ...).
This is already possible I believe, but mostly because browsers avoid
blocking on networking I/O.
Ludo’.
prev parent reply other threads:[~2021-05-11 20:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-01 15:04 FYI: guile-scheme bindings to GNU Mach and the Hurd Joshua Branson
2021-05-01 19:48 ` Maxime Devos
2021-05-02 6:03 ` Mark H Weaver
2021-05-02 20:51 ` Ludovic Courtès
2021-05-04 20:18 ` Maxime Devos
2021-05-06 16:30 ` Ludovic Courtès
2021-05-06 20:58 ` Maxime Devos
2021-05-11 20:29 ` Ludovic Courtès [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o8dhvwse.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=maximedevos@telenet.be \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).