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: Sat, 08 Jul 2023 09:25:20 +0300 Message-ID: <835y6uex7z.fsf@gnu.org> References: <871qhnr4ty.fsf@localhost> <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> <83cz13g811.fsf@gnu.org> <87lefrbvjw.fsf@localhost> <83h6qfecxt.fsf@gnu.org> <87ttuffcnv.fsf@yahoo.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="24576"; 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 Sat Jul 08 08:26:20 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 1qI1Oe-0006CK-Gz for ged-emacs-devel@m.gmane-mx.org; Sat, 08 Jul 2023 08:26:20 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qI1Np-0006QA-1L; Sat, 08 Jul 2023 02:25: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 1qI1Ne-0006P6-2j for emacs-devel@gnu.org; Sat, 08 Jul 2023 02:25:19 -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 1qI1Nd-0006kx-Kc; Sat, 08 Jul 2023 02:25:17 -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=dnZvGwaXG+CbshATv+l9fkJs34zEit2gWs6LN+nONl8=; b=CMHlU4pmFY1x nZPYmQymLjo2n8pVetmJfyUBtDdMgH7gC5xcFRwR8USGkJsvEI1gzAyZmELz+knfXtzeMqMgW2UNi 3Bab8j98PSB87bo42hleppRAlhsrRS4/alBLvxypZ4NZB6hEfJxeMQcOu9YoyfDWSkJoKZC7yF8uh GmymJAFW+H6MHHVM1Wkq6N/wG31vM5GpwWNns7VJQ77M/5orkGiTI4sCWVH7noJrRB7lXxpnYYJSc ki0WY9DanpVfH6ztgUz4QNnkfY4LN9/t7YIHNFJaX1BGS0RIg9ZXvxTVJE3j+PpHca9EBUJo0MABt RuOmSDAYdIT3TriAvoY2nQ==; 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 1qI1Nb-0002Pp-KW; Sat, 08 Jul 2023 02:25:17 -0400 In-Reply-To: <87ttuffcnv.fsf@yahoo.com> (message from Po Lu on Sat, 08 Jul 2023 08:51:48 +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:307596 Archived-At: > From: Po Lu > Cc: Ihor Radchenko , emacs-devel@gnu.org > Date: Sat, 08 Jul 2023 08:51:48 +0800 > > Eli Zaretskii writes: > > > Programs that use async threads avoid global variables like the > > plague. Emacs is full of them. > > That's not true. Look at any modern Unix kernel, and their detailed > locking around traditional Unix data structures, such as allproc, the > run queue, the vnode cache, and et cetera. I said "programs", not "OSes". It _is_ possible to have threads with global variables, but that requires locking, which punishes performance. We even do that in Emacs, with Lisp threads. I thought this discussion was about less painful implementations.