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: Fri, 07 Jul 2023 15:31:20 +0000 Message-ID: <87fs5zbuwn.fsf@localhost> References: <871qhnr4ty.fsf@localhost> <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> <875y6y8nlr.fsf@localhost> <87h6qhnalc.fsf@yahoo.com> <87ilax71wo.fsf@localhost> <831qhli14t.fsf@gnu.org> <87wmzdxewc.fsf@localhost> <83r0plgjeo.fsf@gnu.org> <87o7kpxapo.fsf@localhost> <83mt09gcaf.fsf@gnu.org> <87wmzbc3af.fsf@localhost> <87edljhmjq.fsf@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="38931"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , emacs-devel@gnu.org To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Jul 07 17:32:15 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 1qHnRO-0009wj-QW for ged-emacs-devel@m.gmane-mx.org; Fri, 07 Jul 2023 17:32:14 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qHnQf-0005Z1-SR; Fri, 07 Jul 2023 11:31:29 -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 1qHnQd-0005Yh-6Z for emacs-devel@gnu.org; Fri, 07 Jul 2023 11:31:27 -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 1qHnQY-0001Ge-22 for emacs-devel@gnu.org; Fri, 07 Jul 2023 11:31:25 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id BE247240101 for ; Fri, 7 Jul 2023 17:31:19 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1688743879; bh=bHJylJP1uPrpOQSdE0XAskX+8mawrG6PjwVLDqWv2MY=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=qzjZi2Ttze/ubSwYeA8Fbcxfm4Q153nqYNWRMy2qePvjhKwOi+JYoTK9Swlcy0exJ peEZr3RFbe+VW6aXGN95dM+qYTxgTrkz7gTBHXBU0L5Lmm/6RwFIudLrjKK/cDjA5t IoJjbtPz5IDBGT6YgSkyeCAHNtnOjoxkrSQdzxsiVYxXfRbJjMRYQDfAPvkhfKKEi5 W+eUiDpvhOLCI5rzllFs0h0TmPyTUVDtnxdxHEIcC2J/zf19rb0CJ257mbYwbT1GnE aDdHTXWNr7N2mynq8ha6o3dV/pVglEjBt2m9/EXQuiihS/ifIExXiXyRRAqLdzodCR bDF1s147p1UhQ== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4QyHRq0bKpz9rxH; Fri, 7 Jul 2023 17:31:18 +0200 (CEST) In-Reply-To: <87edljhmjq.fsf@yahoo.com> 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=unavailable 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:307582 Archived-At: Po Lu writes: >> interrupt_input_blocked is more tricky. But it is just one global state >> variable. Surely we can find a solution to make it work with multiple threads. > > interrupt_input_blocked should only be relevant to the thread reading > input, i.e. the main thread. So, we can hold when interrupt_input_blocked is changed until the thread becomes main thread? > The problem with buffer modification lies in two threads writing to the > same buffer at the same time, changing not only the buffer text, but > also PT, ZV, GPT, its markers and its overlay lists. No two threads may > be allowed to modify the buffer simultaneously. Hmm. What about locking thread->current_buffer for all other threads? This appears to solve the majority of the discussed problems. I am not sure how to deal with buffer->pt for multiple threads running in the same buffer. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at