From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.devel Subject: Re: Concurrency via isolated process/thread Date: Tue, 04 Jul 2023 17:52:23 +0000 Message-ID: <87pm57pns8.fsf@localhost> References: <871qhnr4ty.fsf@localhost> <83v8ezk3cj.fsf@gnu.org> <87v8ezpov0.fsf@localhost> <83r0pnk2az.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="25082"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Jul 04 19:53:31 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qGkDS-0006Hw-Mf for ged-emacs-devel@m.gmane-mx.org; Tue, 04 Jul 2023 19:53:30 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qGkCW-0001k2-6q; Tue, 04 Jul 2023 13:52:32 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qGkCU-0001jq-Qx for emacs-devel@gnu.org; Tue, 04 Jul 2023 13:52:30 -0400 Original-Received: from mout02.posteo.de ([185.67.36.66]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qGkCS-0001oK-Gr for emacs-devel@gnu.org; Tue, 04 Jul 2023 13:52:30 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id ECA3A240101 for ; Tue, 4 Jul 2023 19:52:25 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1688493146; bh=hdUOamQ/yIPBfsHJEVTOt+TJoauGmVB9Z8QEIoHPtQo=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=Pn9WQXctmpSfPTHJiGFP84cU4u4zOGQLd8XnxFdP8JcPbAs4/Vux023IzKJrV7iAX 3OMvBd0jhJifAzhQPUahsoELojaHBdTuYRbAdpYxres36SX6A7bFGn4+1sGtXLQqEz w6WdC0DvGvsLCF1rsR5enYEzRjWnNLRgDe3ZJ9lyP6PIL4/DIZuHSPvkeOVcQhaGHb Emqlo+CqX0g6Qjs5n5DM+6efhm/zjXEfU1UbPqqsch6prCa2ZrVsKYdHwLksqphSDu /Gq2ZgCFQ9rSEGdbZJ+OWHYun3XAiSAr+93xmjr1fb7LBiTvdLZXCP3dBv4HH1bDpy jFRQ/3Y9UvUFg== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4QwVk12qnFz9rxD; Tue, 4 Jul 2023 19:52:25 +0200 (CEST) In-Reply-To: <83r0pnk2az.fsf@gnu.org> Received-SPF: pass client-ip=185.67.36.66; envelope-from=yantar92@posteo.net; helo=mout02.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:307438 Archived-At: Eli Zaretskii writes: >> As the first step, I wanted to hear if there is any blocker that >> prevents memcpy between processes without going through print/read. > > I don't think you can design on this base. Security and all that. But why is it a problem? Isn't it normal for a C++ thread to get pointer to the parent heap? For Emacs async process, it can, for example, be a pointer to obarray. > Also, complex structures include pointers and references, which you > cannot safely copy as-is anyway. May you please elaborate? >> IMHO, the main problem with threads is that they cannot be interrupted >> or fire too frequently. > > I wish this were the only problem with threads. Maybe. But I haven't seen other problems preventing threads from being used. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at