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: Wed, 05 Jul 2023 14:00:32 +0000 Message-ID: <875y6y8nlr.fsf@localhost> References: <871qhnr4ty.fsf@localhost> <83v8ezk3cj.fsf@gnu.org> <87v8ezpov0.fsf@localhost> <83r0pnk2az.fsf@gnu.org> <87pm57pns8.fsf@localhost> <87lefvp55t.fsf@yahoo.com> <87sfa28ura.fsf@localhost> <87cz16o8vz.fsf@yahoo.com> <87jzve8r4m.fsf@localhost> <871qhmo5nv.fsf@yahoo.com> <87bkgq8p5t.fsf@localhost> <831qhmjwk0.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="39241"; mail-complaints-to="usenet@ciao.gmane.io" Cc: luangruo@yahoo.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Jul 05 16:01:35 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 1qH34Z-000A2I-6G for ged-emacs-devel@m.gmane-mx.org; Wed, 05 Jul 2023 16:01:35 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qH33m-0006rm-1d; Wed, 05 Jul 2023 10:00:46 -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 1qH33g-0006rW-Dd for emacs-devel@gnu.org; Wed, 05 Jul 2023 10:00:40 -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 1qH33e-0000mQ-Bm for emacs-devel@gnu.org; Wed, 05 Jul 2023 10:00:40 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 1378C240103 for ; Wed, 5 Jul 2023 16:00:35 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1688565636; bh=j83b0Whem7w03ZETBHongTNA0MXiDSxbjh0GEPKoUOI=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=gI17RxI+ATqbE/s+Zu83QhzhWbVk+0xnKlOrZGqVPZ/ArqPb88K/5wyePK6sXHGce c/4Uad4+ARRxFwVIves/cZnd4KBpaBfRWVRLes7yVIekbm9Ftr9BtO/y6OfgsZJ2VC lWfVyJ1oZqAJ+gBr75ES8/w2I+cJdpwRalykYAtoCrqqv4IUmE5LcKpNYR43teAXpS hsJCI+9loGvGzA9r1jxMcMenzClio8o4SiXznaDJDRvwjgpyr9LzHv4e9TJgB8AEWB WjTfccpkw8auK9ENbhj9suELZIwjfajZmI9Sk1kBqLB6lx9EHkZjDeiZyDN5afBA5/ O5e+Q7k7COrkQ== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4Qx1X31FY9z9rxL; Wed, 5 Jul 2023 16:00:35 +0200 (CEST) In-Reply-To: <831qhmjwk0.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:307474 Archived-At: Eli Zaretskii writes: >> AFAIU, one of the big blockers of this is single-threaded GC. Emacs >> cannot free/allocate memory asynchronously. Or do I miss something? > > Why is that a "big blocker"? GC runs "whenever it is convenient" > anyway, so it can be delayed until that time, and run from the main > thread, perhaps sacrificing the memory footprint a bit. Emm. I meant memory allocation. AFAIK, just like GC allocating heap cannot be asynchronous. For the GC, most of the memory objects in long-running Emacs sessions are short-living. So, having a separate GC and memory heap in async process will likely improve the main thread performance GC-wise, as a side effect. > The real "big blocker" is that a typical Emacs session has a huge > global state, which cannot be safely modified by more than a single > thread at a time, and even if one thread writes while the other reads > is in many cases problematic. This too, although isn't is already solved by mutexes? -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at