From: Serissa <stewart@serissa.com>
To: Larry McVoy <lm@mcvoy.com>
Cc: Bakul Shah <bakul@iitbombay.org>,
The Unix Heritage Society mailing list <tuhs@tuhs.org>
Subject: [TUHS] Re: If forking is bad, how about buffering?
Date: Sat, 18 May 2024 21:26:31 -0400 [thread overview]
Message-ID: <F1BC6F9C-3740-4EA6-BA70-95CB032466DC@serissa.com> (raw)
In-Reply-To: <20240519012114.GU9216@mcvoy.com>
MIT's FOS (Factored Operating System) research OS did cross address space copies as part of its messaging machinery.
HPC networking does this by using shared memory (Cross Memory Attach and XPMEM) in a traditional kernel.
-L
> On May 18, 2024, at 9:21 PM, Larry McVoy <lm@mcvoy.com> wrote:
>
> On Sat, May 18, 2024 at 06:04:23PM -0700, Bakul Shah via TUHS wrote:
>> [1] This brings up a separate point: in a microkernel even a simple
>> thing like "foo | bar" would require a third process - a "pipe
>> service", to buffer up the output of foo! You may have reduced
>> the overhead of individual syscalls but you will have more of
>> cross-domain calls!
>
> Do any micro kernels do address space to address space bcopy()?
> --
> ---
> Larry McVoy Retired to fishing http://www.mcvoy.com/lm/boat
next prev parent reply other threads:[~2024-05-19 1:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 13:34 [TUHS] " Douglas McIlroy
2024-05-13 22:01 ` [TUHS] " Andrew Warkentin
2024-05-14 7:10 ` Rob Pike
2024-05-14 11:10 ` G. Branden Robinson
2024-05-15 14:42 ` Dan Cross
2024-05-15 16:42 ` G. Branden Robinson
2024-05-19 1:04 ` Bakul Shah via TUHS
2024-05-19 1:21 ` Larry McVoy
2024-05-19 1:26 ` Serissa [this message]
2024-05-19 1:40 ` Bakul Shah via TUHS
2024-05-19 1:50 ` Bakul Shah via TUHS
2024-05-19 2:02 ` Larry McVoy
2024-05-19 2:28 ` Bakul Shah via TUHS
2024-05-19 2:53 ` Andrew Warkentin
2024-05-19 8:30 ` Marc Rochkind
2024-05-19 2:26 ` Andrew Warkentin
2024-05-19 16:04 ` Paul Winalski
2024-05-14 22:08 ` George Michaelson
2024-05-14 22:34 ` Bakul Shah via TUHS
2024-05-19 10:41 ` Ralph Corderoy
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=F1BC6F9C-3740-4EA6-BA70-95CB032466DC@serissa.com \
--to=stewart@serissa.com \
--cc=bakul@iitbombay.org \
--cc=lm@mcvoy.com \
--cc=tuhs@tuhs.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).