all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Daniel Colascione <dancol@dancol.org>, 31852@debbugs.gnu.org
Subject: bug#31852: Make memory-limit obsolete
Date: Sat, 16 Jun 2018 09:27:30 -0700	[thread overview]
Message-ID: <4725df6e-aaf2-548d-173e-694aa86da918@cs.ucla.edu> (raw)
In-Reply-To: <be5dfedf4cf34b2a51f7999e36d03e00.squirrel@dancol.org>

Daniel Colascione wrote:
> I agree with obsoleting memory-limit. I don't like the vsize patch you
> installed though: what does the amount of address space reserved actually
> tell anyone? There's no relationship to actual resource consumption.

It's not that good a number, true; but it's better than the number we were 
returning, which was typically nonsense.

One of the benefits of moving memory-limit to Lisp was the removal of the bogus 
call to sbrk. Emacs should never call sbrk, and once the portable dumper code is 
merged, Emacs won't ever need to call sbrk again. Yay!

All things considered, I'd rather not go down the rabbit hole of trying to 
improve memory-limit further, because memory-limit was a mistake in the first 
place and nobody uses it (and rightly so) and we should be deprecating it rather 
than trying to improve it. That being said, if you'd like to make it better 
please feel free.





      reply	other threads:[~2018-06-16 16:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-16  1:33 bug#31852: Make memory-limit obsolete Paul Eggert
2018-06-16  6:31 ` Eli Zaretskii
2018-06-16 13:38   ` Paul Eggert
2018-06-16 15:02     ` Eli Zaretskii
2018-06-16 15:34       ` Paul Eggert
2018-06-16 15:51         ` Daniel Colascione
2018-06-16 16:27           ` Paul Eggert [this message]

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=4725df6e-aaf2-548d-173e-694aa86da918@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=31852@debbugs.gnu.org \
    --cc=dancol@dancol.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.