From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Pip Cet via "Emacs development discussions." Newsgroups: gmane.emacs.devel Subject: Re: Some experience with the igc branch Date: Fri, 27 Dec 2024 17:00:26 +0000 Message-ID: <87wmfl3vuy.fsf@protonmail.com> References: <87o713wwsi.fsf@telefonica.net> <86ldw2zy6s.fsf@gnu.org> <87h66p5fy6.fsf@protonmail.com> Reply-To: Pip Cet Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="8261"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Stefan Kangas , Eli Zaretskii , ofv@wanadoo.es, emacs-devel@gnu.org, eller.helmut@gmail.com, acorallo@gnu.org To: =?utf-8?Q?Gerd_M=C3=B6llmann?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Dec 27 20:33:13 2024 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 1tRG59-0001wH-Ql for ged-emacs-devel@m.gmane-mx.org; Fri, 27 Dec 2024 20:33:11 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tRG4C-000217-1t; Fri, 27 Dec 2024 14:32:12 -0500 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 1tRDhf-0007WU-1N for emacs-devel@gnu.org; Fri, 27 Dec 2024 12:00:51 -0500 Original-Received: from mail-10631.protonmail.ch ([79.135.106.31]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tRDha-0003oe-Tc for emacs-devel@gnu.org; Fri, 27 Dec 2024 12:00:46 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1735318831; x=1735578031; bh=FAM+n2zpuDAIQlV++Yy8lGmGZnwC0jWbnolCOTK1Lro=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector:List-Unsubscribe:List-Unsubscribe-Post; b=suekpGO8S7LRYdAEGOH1QK8JV/lDnLEixChgXPN8zgWEx7zU8kM6c/Lp1DG/KEZS6 rlKbnmKkrIqJmwZplmXU2TUNi7h20sSKwrfhbGH9tugrpdy0lcjW0hbaqWlmTfDc4K iGD0GvYWNXZ0f7yFQjkpJ6PEdM9m7WrzpP8l5wldziFROxUf5KyzxMM3puPvVfkP8t WCwe458wLGD1knVYW5FaUdSHS302ANm2FN+p9hU9Tgg7jF5PozZSVowY35rx96VC26 6xP7Fdk/YTvw5z4dTQ3XRbvXbpKW1KYIH02UxtpjsBK/9LBPla3TV9tqpvBhid2nfe eo/3BKVvKLtBg== In-Reply-To: Feedback-ID: 112775352:user:proton X-Pm-Message-ID: ebbe6da2de013c3f87cf052b58752dab94944743 Received-SPF: pass client-ip=79.135.106.31; envelope-from=pipcet@protonmail.com; helo=mail-10631.protonmail.ch X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=unavailable autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Fri, 27 Dec 2024 14:32:10 -0500 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:327225 Archived-At: Gerd M=C3=B6llmann writes: > Pip Cet writes: > >> Gerd M=C3=B6llmann writes: >> >>> Gerd M=C3=B6llmann writes: >>> >>>> I've reached the point where I don't know what else to explain. Could >>>> always be improved, of course, and so on. Please find attached, with >>>> request for feedback. >>> >>> Ahem, just remembered that I had already an admin/igc.org in the branch= , >>> so I've now replaced that with what I've written. >> >> Thank you very much! >> >>> - Concurrent. The GC runs in its own thread. There are no explicit >>> calls to start GC, and Emacs doesn't have to wait for the GC to >>> complete. >> >> I don't think that's true right now (it is what I want for Christmas, >> though). On GNU/Linux, the GC usually runs on the main thread. On >> macOS, the GC can run on the main thread (allocation) or on the SIGSEGV >> handler thread (memory barriers); in both cases, the main thread has to >> wait for it to complete. > > You mean what happens when an allocation point has used up its memory, > and needs to get some more? That's usually what triggers GC here, IME (but then, my experience represents an atypical situation, where we never become idle.) > I haven't looked what percentage of GC time > that takes. Also, the GC steps I didn't mention. > One has to make a cut somewhere. Fair enough. We should never assume that GC runs on the same thread, so writing that it never does may be a justifiable lie here. We also shouldn't assume that it's on a separate thread, but that's only relevant to signal handlers. Pip