From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Newsgroups: gmane.emacs.devel Subject: Re: [ELPA] New package: dired-duplicates Date: Thu, 9 Nov 2023 09:53:37 +0100 Message-ID: References: <87h6m5shpf.fsf@gmail.com> <831qd9a7gg.fsf@gnu.org> <87lebhz78r.fsf@posteo.net> <83sf5p8efg.fsf@gnu.org> <2b30b6e0-d30e-41e1-83a5-05b0c3fa8aa6@gmx.at> <83lebg8zsu.fsf@gnu.org> <715392ae-8ae8-449e-905b-8ff2aa6a2e5a@gmx.at> <837cmr1nja.fsf@gnu.org> <48fece87-5bd9-4d37-a6bb-2e9b9da00bc2@gmx.at> <831qcz1fm3.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="kk9WY2rTd+vGYozl" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="17552"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Harald Judt , emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Nov 09 09:54:36 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 1r10o8-0004Kb-3e for ged-emacs-devel@m.gmane-mx.org; Thu, 09 Nov 2023 09:54:36 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1r10nO-000692-5a; Thu, 09 Nov 2023 03:53:50 -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 1r10nM-00068d-TL for emacs-devel@gnu.org; Thu, 09 Nov 2023 03:53:48 -0500 Original-Received: from mail.tuxteam.de ([5.199.139.25]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1r10nK-000623-Jb; Thu, 09 Nov 2023 03:53:48 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tuxteam.de; s=mail; h=From:In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=RGBAsdx9essmKn7hgeWku7qqmjrFmefUA2r8vmHWXJE=; b=DIlIpokGg1Da6TNh6TxabwNEl3 nCD1IB/LA+/0dIV/fsYiwljIaJIqmwzzPvXz5FutMyyDkLcb/FP+t63Fdu29Ova39qlplRWUPvjS2 W7J0kmkhhRjLkRWzRvlrJqjc97+1mV+uAw8CF2xVzg7iEEzJziEq1M10kCMleITPNg/Jn1OnmptP8 lsUcgYvZNOrBWuZAQHumF7r+2e1pSEUI3QaWXlcpad0Z/TvayWQAXLAD8HIdkmiNx9wolkZ6joYFw /ERe/0GSql9pCaBfmdQTDgu0dzGxr0dw5sTE92Wy3owsZnmCO2Ovk2TRWUkcAZ6hEfUGhh6EQ4blp C8L2e6ng==; Original-Received: from tomas by mail.tuxteam.de with local (Exim 4.94.2) (envelope-from ) id 1r10nB-0007Zd-Pe; Thu, 09 Nov 2023 09:53:37 +0100 Content-Disposition: inline In-Reply-To: <831qcz1fm3.fsf@gnu.org> Received-SPF: pass client-ip=5.199.139.25; envelope-from=tomas@tuxteam.de; helo=mail.tuxteam.de 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, 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:312390 Archived-At: --kk9WY2rTd+vGYozl Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 09, 2023 at 10:43:32AM +0200, Eli Zaretskii wrote: > > Date: Thu, 9 Nov 2023 09:00:11 +0100 > > Cc: emacs-devel@gnu.org > > From: Harald Judt [...] > > Maybe it would be possible to make it dependent on the amount of RAM av= ailable=20 > > on the system? >=20 > Ideally, yes, but in practice knowing how much is available is not > that easy on a modern OS, so I don't think it's worth the hassle, > especially in fallback code. Don't even try :-) No, seriously. There's swap. Depending on tech, using it might be viable (NVME) or not that much (spinning rust). The sysadmin might plug in another 2TB of RAM on request [1] (or the cloud orchestration system might allot to you another 16G chunk). Modern OSes usually overcommit (if you say "malloc" they say "there you go" and fault-in page by page whenever you access them first). Cheers [1] The Linux kernel can pull this kind of tricks; your hardware might, if you have paid the price for that https://www.kernel.org/doc/html/v5.0/admin-guide/mm/memory-hotplug.html --=20 t --kk9WY2rTd+vGYozl Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iFwEABECAB0WIQRp53liolZD6iXhAoIFyCz1etHaRgUCZUyeCwAKCRAFyCz1etHa RkQlAJ9sFP8CroKrHcmgJVN+oMflIJNSYQCVGm5sZg5ZjjNq5O/ts6knK7FMyw== =WmBF -----END PGP SIGNATURE----- --kk9WY2rTd+vGYozl--