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: Sun, 09 Jul 2023 16:12:32 +0300 Message-ID: <83h6qd9qkf.fsf@gnu.org> References: <871qhnr4ty.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> <83cz13g811.fsf@gnu.org> <87lefrbvjw.fsf@localhost> <83h6qfecxt.fsf@gnu.org> <875y6vbiej.fsf@localhost> <834jmeew2u.fsf@gnu.org> <87a5w6aa89.fsf@localhost> <838rbqcvlx.fsf@gnu.org> <87mt058l1b.fsf@localhost> <87wmz9cm0p.fsf@yahoo.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3572"; mail-complaints-to="usenet@ciao.gmane.io" Cc: yantar92@posteo.net, emacs-devel@gnu.org To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jul 09 15:13:17 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 1qIUE1-0000jq-8w for ged-emacs-devel@m.gmane-mx.org; Sun, 09 Jul 2023 15:13:17 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qIUDD-00068P-9u; Sun, 09 Jul 2023 09:12:27 -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 1qIUDC-00068B-2F for emacs-devel@gnu.org; Sun, 09 Jul 2023 09:12:26 -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 1qIUDB-0000IM-P9; Sun, 09 Jul 2023 09:12:25 -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=OsvamMfSd/SHwhRX9yNIVN8c0F1PkaQ2UzHMTp5UQIE=; b=BU6jZIfmJ3zc y7kZTD1uD5P+w13JmNiueeA7yC5t+5XKNeGCDhGdEbkFnprj4kT8paxDRX6HlW5Uhi0mFHmFWY5hO vomYhg3kc0T63bqylDbScySgB1OpwsIjteKBcETZeX8748ANumWuqcls9Pxo/L6kbDwyWGacLtnYX xts9hhsCny5Ri4BfOhuJ6Y8oP8VQrc4/ZMfhnW/2bcqsUHjPKA9V6if/rAumwfOdP/OnmV9zoaFZI he0FvOSOOqjrf5HmvlRP6hADEVP0JCnEuMBOQkTeU/8GL//OH9sYLqRpsZj1bBGXZBKIoOQ3HoJ3k S3IeFzZnXhmFKUKj4SluiA==; 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 1qIUDB-00069c-97; Sun, 09 Jul 2023 09:12:25 -0400 In-Reply-To: <87wmz9cm0p.fsf@yahoo.com> (message from Po Lu on Sun, 09 Jul 2023 20:22:30 +0800) 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:307676 Archived-At: > From: Po Lu > Cc: Eli Zaretskii , emacs-devel@gnu.org > Date: Sun, 09 Jul 2023 20:22:30 +0800 > > >> Sure. Like I said: we'd need to lock everything. > > But the interlocking will be specific to the object being locked. Two > threads will be able to modify the marker lists of two distinct buffers > simultaneously. For this particular example, yes. But we also have a lot of global objects that are not specific to a buffer or a window. Example: buffer-list. Another example: Vwindow_list (not exposed to Lisp). Etc. etc.