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: Mon, 24 Jul 2023 08:42:52 +0000 Message-ID: <878rb53dkj.fsf@localhost> References: <871qhnr4ty.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> <838rbrg4mg.fsf@gnu.org> <87ilavbvdr.fsf@localhost> <834jmffvhy.fsf@gnu.org> <878rbrbmwr.fsf@localhost> <83fs5zecpo.fsf@gnu.org> <87351zbi72.fsf@localhost> <83351yevde.fsf@gnu.org> <87cz12ad2w.fsf@localhost> <83a5w6cwdr.fsf@gnu.org> <87pm518m0g.fsf@localhost> <83o7kl9tyj.fsf@gnu.org> <874jmd89us.fsf@localhost> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="35421"; 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 Mon Jul 24 10:43:48 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 1qNrAR-000928-LW for ged-emacs-devel@m.gmane-mx.org; Mon, 24 Jul 2023 10:43:47 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qNr9S-0005EY-Hp; Mon, 24 Jul 2023 04:42: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 1qNr9Q-0005E3-1s for emacs-devel@gnu.org; Mon, 24 Jul 2023 04:42:44 -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 1qNr9N-0005xk-QE for emacs-devel@gnu.org; Mon, 24 Jul 2023 04:42:43 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 546A6240103 for ; Mon, 24 Jul 2023 10:42:39 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1690188159; bh=KPIxPGsianemeCKPhdktfTZ89MX6+i4L1r/0UTmbRUE=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=EzqzbhHbE/s9HYkdEl3Bnu4rJ/VTpHn/Hs38e+YU0FqiyvQ3RlWuTraNb/xX4EMtJ xUQBVCNxdyi+/7ivuHmoUwXOzlKiaQDFz30YkhXRoLEC351FEdCJa3KRXKyltcQHhT GwXwUuI6x82XyS0/FQk4SqIWdFhhJvhz4WELw9O6Y3TeP3YFcUCG8W1BXXVUPEb2Iy yVGaw7xwHRIUp/yUGZttZ0I5Pfu/CgmtbMHd/DPfuNSvzIz5V/p01kH+SWXAtKAeFC UlrGUnXaERrlTUJEZNaR5h77MOGCtY9f4PiXOrxWfWtAMJePiX1iHFWdKtL5LC92l7 a8aQKMMKEAUvA== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4R8YZQ4lVqz9s1c; Mon, 24 Jul 2023 10:42:38 +0200 (CEST) In-Reply-To: <874jmd89us.fsf@localhost> Received-SPF: pass client-ip=185.67.36.66; envelope-from=yantar92@posteo.net; helo=mout02.posteo.de X-Spam_score_int: -53 X-Spam_score: -5.4 X-Spam_bar: ----- X-Spam_report: (-5.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=-1, RCVD_IN_MSPIKE_WL=-0.01, 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:308045 Archived-At: Ihor Radchenko writes: > 3. Current buffer, point position, and narrowing. > > By current design, Emacs always have a single global current buffer, > current point position, and narrowing state in that buffer. > Even when we switch cooperative threads, a thread must update its > thread->current_buffer to previous_thread->current_buffer; and update > point and narrowing by calling set_buffer_internal_2. > > Current design is incompatible with async threads - they must be able > to have different buffers, points, and narrowing states current > within each thread. > > That's why I suggested to convert PT, BEGV, and ZV into > thread-locals. Would it be acceptable to convert buffer PT, BEGV, and ZV into thread-local for current cooperative threads? I am thinking about: 1. Removing pt, pt_byte, begv, begv_byte, zv, zv_byte, pt_marker_, begv_marker_, and zv_marker_ from buffer objects. 2. Adding pt/begv/zv to thread object. 3. Adding an alist linking buffers and past pt/begv/zv positions visited by a given thread. This way, when a thread yields and later continues executing, its point and restriction will not be changed. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at