From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Concurrency via isolated process/thread Date: Fri, 07 Jul 2023 17:47:51 +0300 Message-ID: <838rbrg4mg.fsf@gnu.org> References: <871qhnr4ty.fsf@localhost> <87jzve8r4m.fsf@localhost> <871qhmo5nv.fsf@yahoo.com> <87bkgq8p5t.fsf@localhost> <831qhmjwk0.fsf@gnu.org> <875y6y8nlr.fsf@localhost> <87h6qhnalc.fsf@yahoo.com> <87ilax71wo.fsf@localhost> <878rbtkz2c.fsf@yahoo.com> <87a5w96x2o.fsf@localhost> <87jzvdjjp4.fsf@yahoo.com> <877crd6w53.fsf@localhost> <877crdjiwn.fsf@yahoo.com> <874jmh6v4s.fsf@localhost> <83y1jtgmbw.fsf@gnu.org> <87zg49xfke.fsf@localhost> <83sfa1gjns.fsf@gnu.org> <87r0plxbep.fsf@localhost> <83ilawhpi6.fsf@gnu.org> <87zg48apwr.fsf@localhost> <83edljg8ub.fsf@gnu.org> <87o7knbxr7.fsf@localhost> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="9953"; mail-complaints-to="usenet@ciao.gmane.io" Cc: luangruo@yahoo.com, emacs-devel@gnu.org To: Ihor Radchenko Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Jul 07 16:48:34 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 1qHml7-0002MQ-S5 for ged-emacs-devel@m.gmane-mx.org; Fri, 07 Jul 2023 16:48:33 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qHmkR-0002oR-Jm; Fri, 07 Jul 2023 10:47:51 -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 1qHmkQ-0002oI-KA for emacs-devel@gnu.org; Fri, 07 Jul 2023 10:47:50 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qHmkP-0007Hg-DH; Fri, 07 Jul 2023 10:47:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=ODWSHw/UKYR9IznwSLa5g73AWV4PCuLWycIyxX2X3Sg=; b=Dp2MsZ1Sej4E Tjm7YhjP+m3hc/q3oe7SrJAYopTlDGsgh6Rx8Ys233yLHcqIrTKOtbFZflN5vk0xhp9V0AZ5oRtXs EwuW34VZW4EjrHY8MxHnTKy+FQ5fm33MRCsmoRoz/0/s3kcqIqgHmSOcdk6edwNBZyX9RjtLv+/G8 k9oRKovArIfalql6apCb8b3z74Imumu6ynuXbLrVJeIw72DGnqQ/OWO9R2pCCMqdcuG/A5YNCu138 6O1dG9120zDeGh9vnRL8XK8k9O76v/Ik08s1Ld7AqLThErrIfNvH5sKmTEHec0Cavi2vfWkTI+3kw rJ2cB3hcm4kfVaOQdRZUiA==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qHmkO-0002G0-TZ; Fri, 07 Jul 2023 10:47:49 -0400 In-Reply-To: <87o7knbxr7.fsf@localhost> (message from Ihor Radchenko on Fri, 07 Jul 2023 14:29:48 +0000) 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:307579 Archived-At: > From: Ihor Radchenko > Cc: luangruo@yahoo.com, emacs-devel@gnu.org > Date: Fri, 07 Jul 2023 14:29:48 +0000 > > What GC is doing may affect C pointers to internal representations of > Elisp objects. But never the Lisp representations. What do you mean by "Lisp representation"? > So, GC running only matters during a subroutine execution. And not every > subroutine - just for a subset where we directly work with internal > object structs. We always do work with the internal object structs. > The subroutines that are GC-sensitive will need to set and release the > object lock before/after they are done working with that object. That > object lock type will be set in C code directly and will not be > available from Elisp. You are describing something that is not Emacs. > > You are trying to solve what constitutes a very small, almost > > negligible, part of the problem. The elephant in the room is > > something else. > > Ok. Please, describe the elephant in details. I already did: it's the huge global state used implicitly by every Lisp program out there.