GNU bug report logs - #54698
non-recursive GC marking [PATCH]

Previous Next

Full log

Message #100 received at 54698 <at> debbugs.gnu.org (full text, mbox):

From: Po Lu <luangruo <at> yahoo.com>
To: Richard Stallman <rms <at> gnu.org>
Cc: larsi <at> gnus.org, mattiase <at> acm.org, eliz <at> gnu.org, 54698 <at> debbugs.gnu.org,
 p.stephani2 <at> gmail.com
Subject: Re: bug#54698: non-recursive GC marking [PATCH]
Date: Fri, 08 Apr 2022 13:49:18 +0800

Richard Stallman <rms <at> 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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.