From: Pavel Begunkov <[email protected]>
To: Askar Safin <[email protected]>
Cc: axboe <[email protected]>, io-uring <[email protected]>,
josh <[email protected]>, krisman <[email protected]>
Subject: Re: [PATCH RFC 0/9] Launching processes with io_uring
Date: Thu, 23 Jan 2025 00:31:26 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 1/22/25 23:49, Askar Safin wrote:
> ---- On Sun, 19 Jan 2025 07:03:51 +0400 Pavel Begunkov wrote ---
> > I also wonder, if copying the page table is a performance problem, why
> > CLONE_VM + exec is not an option?
>
> Do you mean CLONE_VFORK? Anyway, CLONE_VM surprisingly turns out
No, vfork is troublesome. What I mean is a task that shares
the page table, or in other words a vfork that doesn't block
and has a dedicated stack.
> to be a good solution. So thank you!
>
> There is a bug in libc or in Linux: https://sourceware.org/bugzilla/show_bug.cgi?id=32565 .
>
> I suspect this is actually a Linux bug.
>
> After receiving your letter I decided to try CLONE_VM. And it works!
> There is no bug in CLONE_VM version! You can see more details here:
> https://www.openwall.com/lists/musl/2025/01/22/1
I haven't looked at the bug, but IIUC fundamentally posix_spawn()
does the same thing, and if so it's likely that any problem you
have with posix_spawn() could be triggered for your hand crafted
version.
--
Pavel Begunkov
next prev parent reply other threads:[~2025-01-23 0:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 23:43 [PATCH RFC 0/9] Launching processes with io_uring Gabriel Krisman Bertazi
2024-12-09 23:43 ` [PATCH RFC 1/9] io_uring: Drop __io_req_find_next_prep Gabriel Krisman Bertazi
2024-12-09 23:43 ` [PATCH RFC 2/9] io_uring: Expose failed request helper in internal header Gabriel Krisman Bertazi
2024-12-09 23:43 ` [PATCH RFC 3/9] kernel/fork: Don't inherit PF_USER_WORKER from parent Gabriel Krisman Bertazi
2024-12-09 23:43 ` [PATCH RFC 4/9] fs/exec: Expose do_execveat symbol Gabriel Krisman Bertazi
2024-12-09 23:43 ` [PATCH RFC 5/9] kernel/fork: Add helper to fork from io_uring Gabriel Krisman Bertazi
2024-12-09 23:43 ` [PATCH RFC 6/9] io_uring: Let commands run with current credentials Gabriel Krisman Bertazi
2024-12-11 14:48 ` Pavel Begunkov
2024-12-09 23:43 ` [PATCH RFC 7/9] io_uring: Introduce IORING_OP_CLONE Gabriel Krisman Bertazi
2024-12-11 13:37 ` Pavel Begunkov
2024-12-11 17:26 ` Josh Triplett
2024-12-17 11:03 ` Pavel Begunkov
2024-12-17 19:14 ` Josh Triplett
2024-12-09 23:43 ` [PATCH RFC 8/9] io_uring: Let ->issue know if it was called from spawn thread Gabriel Krisman Bertazi
2024-12-09 23:43 ` [PATCH RFC 9/9] io_uring: Introduce IORING_OP_EXEC command Gabriel Krisman Bertazi
2024-12-10 21:01 ` Josh Triplett
2024-12-10 21:10 ` [PATCH RFC 0/9] Launching processes with io_uring Josh Triplett
2024-12-11 14:02 ` Pavel Begunkov
2024-12-11 17:34 ` Josh Triplett
2024-12-13 20:13 ` Gabriel Krisman Bertazi
2024-12-17 16:10 ` Pavel Begunkov
2024-12-30 23:38 ` Gabriel Krisman Bertazi
2024-12-31 14:35 ` Pavel Begunkov
2025-01-18 22:33 ` Askar Safin
2025-01-19 3:04 ` Pavel Begunkov
2025-01-22 23:49 ` Askar Safin
2025-01-23 0:31 ` Pavel Begunkov [this message]
2025-01-23 1:10 ` Pavel Begunkov
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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