From: <tomas@tuxteam.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Harald Judt <h.judt@gmx.at>, emacs-devel@gnu.org
Subject: Re: [ELPA] New package: dired-duplicates
Date: Thu, 9 Nov 2023 09:53:37 +0100 [thread overview]
Message-ID: <ZUyeESpUysf7nViV@tuxteam.de> (raw)
In-Reply-To: <831qcz1fm3.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1090 bytes --]
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 <h.judt@gmx.at>
[...]
> > Maybe it would be possible to make it dependent on the amount of RAM available
> > on the system?
>
> 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
--
t
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2023-11-09 8:53 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 10:34 [ELPA] New package: dired-duplicates Harald Judt
2023-10-31 12:21 ` Philip Kaludercic
2023-10-31 21:05 ` Harald Judt
2023-11-01 2:14 ` Michael Heerdegen
2023-11-01 15:16 ` [External] : " Drew Adams
2023-11-01 15:45 ` Eli Zaretskii
2023-11-01 16:28 ` Drew Adams
2023-11-01 16:47 ` Eli Zaretskii
2023-11-01 16:33 ` Philip Kaludercic
2023-11-01 11:32 ` Philip Kaludercic
2023-11-01 20:04 ` Harald Judt
2023-11-01 21:29 ` Philip Kaludercic
2023-11-02 8:44 ` Harald Judt
2023-11-03 8:19 ` Philip Kaludercic
2023-11-03 20:19 ` Harald Judt
2023-11-04 15:27 ` Philip Kaludercic
2023-11-06 9:33 ` Harald Judt
2023-11-10 8:37 ` Philip Kaludercic
2023-11-10 10:02 ` Harald Judt
2023-11-23 6:12 ` Philip Kaludercic
2023-10-31 21:24 ` Harald Judt
2023-11-01 17:40 ` Stefan Kangas
2023-11-01 3:30 ` Eli Zaretskii
2023-11-01 13:53 ` Visuwesh
2023-11-01 14:12 ` Eli Zaretskii
2023-11-01 17:57 ` Philip Kaludercic
2023-11-01 19:24 ` Eli Zaretskii
2023-11-01 20:09 ` Harald Judt
2023-11-02 5:55 ` Eli Zaretskii
2023-11-08 20:29 ` Harald Judt
2023-11-09 5:52 ` Eli Zaretskii
2023-11-09 8:00 ` Harald Judt
2023-11-09 8:38 ` tomas
2023-11-09 8:48 ` Eli Zaretskii
2023-11-09 8:43 ` Eli Zaretskii
2023-11-09 8:53 ` tomas [this message]
2023-11-09 9:18 ` Harald Judt
2023-11-09 14:52 ` Harald Judt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZUyeESpUysf7nViV@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=h.judt@gmx.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.