From: Davide Libenzi <davidel@xmailserver.org>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFD] Combined fork-exec syscall.
Date: Sun, 27 Apr 2003 20:03:12 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.50.0304271957210.7601-100000@blue1.dev.mcafeelabs.com> (raw)
On Sun, 27 Apr 2003, Ulrich Drepper wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Davide Libenzi wrote:
>
> > This is very much library stuff. I don't think that saving a couple of
> > system calls will give you an edge, expecially when we're talking of
> > spawning another process. Even if the process itself does nothing but
> > return. Ulrich might be eventually interested ...
>
> POSIX has a spawn interface, see <spawn.h> on modern systems.
^^^^^^^^^^^^^^
( You want to make me pay for the last question about swapcontext in our
old glibc environment, don't you ? ;)
If I read the specification correctly, the posix_spwan() interface will
not solve scalability problems due to huge file tables. If I read it
correctly, and if you have M files currently opened and you want to
keep/dup only three files, you have to drop (M-3) close actions plus 3 dup
actions. To solve such problem you'd need a default-all-closed option plus
3 dup actions. That inside the kernel will translate in a brand new file
table plus 3 links.
- Davide
next reply other threads:[~2003-04-28 2:50 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-28 3:03 Davide Libenzi [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-28 0:57 [RFD] Combined fork-exec syscall Mark Grosberg
2003-04-28 0:59 ` Larry McVoy
2003-04-28 1:16 ` Mark Grosberg
2003-04-28 1:36 ` Måns Rullgård
2003-04-28 1:45 ` Mark Grosberg
2003-04-28 1:49 ` dean gaudet
2003-04-28 1:59 ` Mark Grosberg
2003-04-28 2:27 ` Miles Bader
2003-04-28 19:07 ` dean gaudet
2003-05-01 13:14 ` Jakob Oestergaard
2003-04-28 1:17 ` Davide Libenzi
2003-04-28 1:28 ` Mark Grosberg
2003-04-29 2:01 ` Rafael Costa dos Santos
2003-04-28 1:41 ` Ulrich Drepper
2003-04-28 1:49 ` Mark Grosberg
2003-04-28 2:19 ` Ulrich Drepper
2003-04-28 6:59 ` Kai Henningsen
2003-04-28 1:35 ` dean gaudet
2003-04-28 1:43 ` Mark Grosberg
2003-04-28 3:44 ` Mark Mielke
2003-04-28 5:16 ` Jamie Lokier
2003-04-28 2:38 ` Davide Libenzi
2003-04-28 2:09 ` Richard B. Johnson
2003-04-28 2:12 ` Mark Grosberg
2003-04-28 2:42 ` Werner Almesberger
2003-04-28 6:35 ` Mark Grosberg
2003-04-29 2:47 ` Rafael Santos
2003-04-28 3:20 ` Werner Almesberger
2003-04-28 13:00 ` Richard B. Johnson
2003-04-28 13:22 ` Andreas Schwab
2003-04-28 13:57 ` Richard B. Johnson
2003-04-28 13:57 ` Andreas Schwab
2003-04-28 14:16 ` Richard B. Johnson
2003-04-28 14:38 ` Valdis.Kletnieks
2003-04-28 14:56 ` Richard B. Johnson
2003-04-28 14:42 ` Andreas Schwab
2003-04-28 16:36 ` Mark Grosberg
2003-04-28 17:19 ` Davide Libenzi
2003-04-28 18:28 ` Craig Ruff
2003-05-06 2:48 ` Miles Bader
2003-04-29 18:50 ` Timothy Miller
2003-04-28 2:32 ` Werner Almesberger
2003-04-28 7:40 ` Mirar
2003-04-28 12:45 ` Matthias Andree
2003-04-29 1:05 ` Rafael Costa dos Santos
2003-04-28 1:19 ` Mark Grosberg
2003-04-29 1:29 ` Rafael Costa dos Santos
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=Pine.LNX.4.50.0304271957210.7601-100000@blue1.dev.mcafeelabs.com \
--to=davidel@xmailserver.org \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.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).