From: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
To: Rob Landley <rob@landley.net>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux Embedded <linux-embedded@vger.kernel.org>,
Oleg Nesterov <oleg@redhat.com>,
dalias@libc.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: execve(NULL, argv, envp) for nommu?
Date: Mon, 11 Sep 2017 19:14:38 +0100 [thread overview]
Message-ID: <20170911191438.3221e95e@alans-desktop> (raw)
In-Reply-To: <ab6e6e8b-7040-a07d-5502-405701182568@landley.net>
> It's not the performance cost, it's rewriting all the pointers.
Which you don't need to do
> Without address translation, copying the existing mappings to a new
> range requires finding and adjusting every pointer to the old data,
No it doesn't. See Minix.
When you fork() rather than vfork you stick a copy of any non-relocatable
elements (typically DATA copy + BSS + stack with a sane CPU and compiler)
into a buffer and you swap them over with the real copy when you task
switch to the one in the wrong place. If you start the child first you
usually only take one copy.
I've always been amused that Linux NOMMU hasn't managed to grow a feature
that people successfully implemented on 68000 long long ago, and I
believe some other processors back to v6/v7 days.
Alan
prev parent reply other threads:[~2017-09-11 18:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 7:34 execve(NULL, argv, envp) for nommu? Rob Landley
2017-09-05 9:00 ` Geert Uytterhoeven
2017-09-05 13:24 ` Alan Cox
2017-09-06 1:12 ` Rob Landley
2017-09-08 21:18 ` Rob Landley
2017-09-11 15:15 ` Oleg Nesterov
2017-09-12 10:48 ` Rob Landley
2017-09-12 11:30 ` Geert Uytterhoeven
2017-09-12 13:45 ` Rob Landley
2017-09-13 19:33 ` Alan Cox
2017-09-12 15:45 ` Oleg Nesterov
2017-09-13 14:20 ` Oleg Nesterov
2017-09-11 18:14 ` Alan Cox [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170911191438.3221e95e@alans-desktop \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=dalias@libc.org \
--cc=geert@linux-m68k.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=rob@landley.net \
/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).