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 12:25:40 +0000 Message-ID: <87wmyp1oor.fsf@localhost> References: <871qhnr4ty.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> <878rb53dkj.fsf@localhost> <87wmyp1vr9.fsf@yahoo.com> <875y6939jl.fsf@localhost> <87jzup1p4x.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="36178"; 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 Mon Jul 24 14:26:24 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 1qNuds-00099z-HG for ged-emacs-devel@m.gmane-mx.org; Mon, 24 Jul 2023 14:26:24 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qNud6-0008Lp-VS; Mon, 24 Jul 2023 08:25:37 -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 1qNud3-0008LM-SC for emacs-devel@gnu.org; Mon, 24 Jul 2023 08:25:33 -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 1qNud1-00088D-IA for emacs-devel@gnu.org; Mon, 24 Jul 2023 08:25:33 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 0D6C5240101 for ; Mon, 24 Jul 2023 14:25:28 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1690201529; bh=vB25VTM6CVIkruvPDoH+BKUBxKiBw6tIuMvmZcYlhy4=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=f51SGKoAxBm0A1vf9JQ3y2KZjCOmyIlB8uslzD8P5Q/T5YOPFC+IOJqWRaqHyJWdj VWs8Yp133GJLhK7NVsFVBdAC90K9Hbf6HCTMU5TdVUHnDhYYarWwSEMoEZBZ0CPLqS YM8BNxLNtOkBSkb1t72mN/NuPm7mJlaLKGO6uQoxVik3BzrClGJ1aPV9alt4hvQueA IwgxmS/F5663/vDydemeB5dS8XsdDk/SR8d7zmQpNZ4dFlbQMCTbsmYYniwOc/Oaet 42W5FgLxrHdra6QmMeNhVcxPIZGTg27amS9DJiia5ey3Ugs0t3hvdy0ar/fPGh+0Ew wlCvJzghnN7/Q== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4R8fWV6YwTz6v0q; Mon, 24 Jul 2023 14:25:26 +0200 (CEST) In-Reply-To: <87jzup1p4x.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=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:308051 Archived-At: Po Lu writes: > No matter where thread local points are stored, each of these points > will need to be a marker, because text editing operations will otherwise > cause PT in other threads to be desynchronized with PT_BYTE within > multibyte buffers. Both unibyte buffers and multibyte buffers will also > experience complications if a thread deletes text within a buffer, > reducing its size below point within another thread. > > Each text editing operations must then loop through and update each of > these markers. > ... What you are proposing is a fundamental change to the > performance attributes of some of the most basic operations performed by > Emacs, and is not acceptable. But editing operations already loop over all the buffer markers. If a just dozen of extra buffer markers (one for each thread, in the worse case) are unacceptable, we should really do something about marker performance. >> I propose to remove buffer points completely and use thread points >> instead. > > IMHO, any change that increases the number of objects that store points > will be a mistake. There is only one buffer, but there can be many > threads. Last time I wrote a thread code that had to work with buffer text, I had to store markers manually anyway. Otherwise, point position were always chaotic. And threads that will not work with buffer text, will only need to store a single marker. So, I do not see how the proposed approach will make things worse memory-wise. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at