From: Eli Zaretskii <eliz@gnu.org>
To: George Plymale II <georgie@southernohio.net>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Does Emacs return memory to the system on Mac OS X or *BSD?
Date: Wed, 10 May 2017 19:45:30 +0300 [thread overview]
Message-ID: <831srwbqz9.fsf@gnu.org> (raw)
In-Reply-To: <m0vap9ql3m.fsf@lehi.dev.orbitalimpact.com> (message from George Plymale II on Wed, 10 May 2017 02:31:09 -0400)
> From: George Plymale II <georgie@southernohio.net>
> Date: Wed, 10 May 2017 02:31:09 -0400
> Cc: emacs-devel@gnu.org
>
> Well, again, which source file(s) may I poke at to see this sort of
> stuff in action myself?
If you are asking about the Emacs sources, then the relevant suspects
are gmalloc.c and ralloc.c, but each one of these is only relevant to
your build if you see the corresponding *.o file in the build
directory.
The other relevant part is the use of mmap for buffer text; look in
src/config.h for the definition of USE_MMAP_FOR_BUFFERS.
next prev parent reply other threads:[~2017-05-10 16:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 23:03 Does Emacs return memory to the system on Mac OS X or *BSD? George Plymale II
2017-05-10 3:07 ` Stefan Monnier
2017-05-10 6:31 ` George Plymale II
2017-05-10 12:06 ` Stefan Monnier
2017-05-10 16:09 ` George Plymale II
2017-05-13 17:07 ` Andreas Politz
2017-05-10 12:49 ` Stefan Monnier
2017-05-10 16:45 ` Eli Zaretskii [this message]
2017-05-10 19:16 ` George Plymale II
2017-05-10 22:33 ` Tim Cross
2017-05-10 23:34 ` George Plymale II
2017-05-11 0:25 ` Stefan Monnier
2017-05-11 1:39 ` George Plymale II
2017-05-11 2:20 ` Stefan Monnier
2017-05-11 0:06 ` Stefan Monnier
2017-05-11 2:36 ` Eli Zaretskii
2017-05-11 12:29 ` Stefan Monnier
2017-05-11 15:23 ` Eli Zaretskii
2017-05-11 15:39 ` Stefan Monnier
2017-05-11 16:07 ` Eli Zaretskii
2017-05-11 18:52 ` Davis Herring
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=831srwbqz9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=georgie@southernohio.net \
--cc=monnier@iro.umontreal.ca \
/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.