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: roadmap for a multi-threaded, multi-core Emacs? Date: Wed, 04 Oct 2023 10:33:27 +0300 Message-ID: <83jzs26dvc.fsf@gnu.org> References: <87r0mcfwod.fsf@dataswamp.org> <83il7o6xx4.fsf@gnu.org> <87pm1vebe1.fsf@dataswamp.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="6467"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Emanuel Berg Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Oct 04 09:34:19 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 1qnwOg-0001Ny-Ee for ged-emacs-devel@m.gmane-mx.org; Wed, 04 Oct 2023 09:34:19 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qnwNq-0005xJ-Gv; Wed, 04 Oct 2023 03:33:26 -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 1qnwNp-0005wW-34 for emacs-devel@gnu.org; Wed, 04 Oct 2023 03:33:25 -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 1qnwNo-00043E-4U; Wed, 04 Oct 2023 03:33:24 -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=jaN87+CSQ5WNbcFxjUQ35YQ9LhKJSO81ZqhpFHod8yM=; b=pImUHyhL6D+Y 8p+5tyD/kD7vqfN6+hV8bLfggutC0ktfdKmjB4AGM7iPucny7FKpvJZRvFRQ4HjFslbCRD+pGoH/q Afsp8T3Ft3WVYCHNTgEKjquNE3BF3EE8H4AUq6GDodXSAoaLQoavypCUkI2EjL0j7JpTsDOsGUebD uKt/dy7RaNHuByFu6x020ZudTp+sOnyyTiuI7GvgblxBIq3cjWXZmoKN+roBZJjBgReZSOzGmEyWd 2G/4qsKYUmBzDn6jKG9ptQn3RSRwmKD0yRJflBA/4vnkef+AmWQxtbS3uDUDLmCZ1545X1SI3s1Rw qWhGQHdkNXmc5Anag6Lvpg==; In-Reply-To: <87pm1vebe1.fsf@dataswamp.org> (message from Emanuel Berg on Tue, 03 Oct 2023 21:47:34 +0200) 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:311261 Archived-At: > From: Emanuel Berg > Date: Tue, 03 Oct 2023 21:47:34 +0200 > > Eli Zaretskii wrote: > > >> What I mean is, do we have a plan for that to > >> happen, ultimately? > > > > We have general goals, not a detailed plan with specific > > changes in various Emacs subsystems. Figuring out the > > (non-trivial) details is part of the job, I think, as there > > can be different approaches with correspondingly different > > trade-offs. > > Is there a document or anything where efforts are coordinated? > > General or detailed? Not that I know of. Primarily, IMO, because there are no efforts yet to coordinate.