From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Richard Stallman <rms@gnu.org>
Cc: larsi@gnus.org, mattiase@acm.org, eliz@gnu.org,
54698@debbugs.gnu.org, p.stephani2@gmail.com
Subject: bug#54698: non-recursive GC marking [PATCH]
Date: Fri, 08 Apr 2022 13:49:18 +0800 [thread overview]
Message-ID: <87pmlsw2e9.fsf@yahoo.com> (raw)
In-Reply-To: <E1ncgAC-00064w-N6@fencepost.gnu.org> (Richard Stallman's message of "Fri, 08 Apr 2022 00:24:00 -0400")
Richard Stallman <rms@gnu.org> writes:
> Concretely, what is this "knob"? Is it a per-process variable? If
> so, we could make Emacs set it, with a Lisp function to specify the
> value.
It's a kernel parameter. It's not per-process, it applies to the entire
system. Emacs could set it, but it would typically not have sufficient
privileges to do so.
> What is the precise definition of "no more memory left"?
It's complicated. I think in addition to checking for free pages, Linux
also tries to reclaim some cached data, and the inode cache, before
determining that there is really no memory left.
> The thrashing that I observed did not immediately kill any process.
> Rather, it continued for minutes before doing so. So I don't think
> there was "no more memory left on the system", because if that had
> been the case, Linux would have known it immediately.
Yes, the OOM killer typically kicks in before there is really no memory
left.
next prev parent reply other threads:[~2022-04-08 5:49 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-03 18:40 bug#54698: non-recursive GC marking [PATCH] Mattias Engdegård
2022-04-04 11:01 ` Lars Ingebrigtsen
2022-04-04 11:16 ` Mattias Engdegård
2022-04-04 11:29 ` Lars Ingebrigtsen
2022-04-04 11:31 ` Lars Ingebrigtsen
2022-04-04 11:38 ` Eli Zaretskii
2022-04-04 11:57 ` Mattias Engdegård
2022-04-04 12:25 ` Eli Zaretskii
2022-04-04 17:18 ` Mattias Engdegård
2022-04-05 1:15 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-05 8:08 ` Mattias Engdegård
2022-04-05 8:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-05 11:11 ` Mattias Engdegård
2022-04-05 11:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-05 11:43 ` Eli Zaretskii
2022-04-05 12:31 ` Philipp Stephani
2022-04-05 13:12 ` Eli Zaretskii
2022-04-06 4:09 ` Richard Stallman
2022-04-06 5:48 ` Phil Sainty
2022-04-06 10:59 ` Eli Zaretskii
2022-04-06 12:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-06 12:23 ` Eli Zaretskii
2022-04-06 12:34 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-06 14:10 ` Eli Zaretskii
2022-04-06 12:52 ` Lars Ingebrigtsen
2022-04-08 4:24 ` Richard Stallman
2022-04-08 5:49 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-04-08 6:16 ` Eli Zaretskii
2022-04-08 7:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-08 11:15 ` Eli Zaretskii
2022-04-08 11:32 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-08 11:55 ` Lars Ingebrigtsen
2022-04-08 11:58 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-08 12:07 ` Lars Ingebrigtsen
2022-04-08 12:16 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-08 13:07 ` Lars Ingebrigtsen
2022-04-09 0:28 ` Phil Sainty
2022-04-08 12:13 ` Eli Zaretskii
2022-04-04 14:32 ` Andrea Corallo
2022-04-04 14:39 ` Mattias Engdegård
2022-04-04 15:44 ` Andrea Corallo
2022-04-04 16:04 ` Mattias Engdegård
2022-04-05 9:10 ` Andrea Corallo
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=87pmlsw2e9.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=54698@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--cc=mattiase@acm.org \
--cc=p.stephani2@gmail.com \
--cc=rms@gnu.org \
/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.