From: Matt Wette <matt.wette@gmail.com>
To: guile-user@gnu.org
Subject: Re: mmap for guile
Date: Mon, 4 Jul 2022 05:59:31 -0700 [thread overview]
Message-ID: <5e2f37dc-58a4-817f-f088-593fddcdf95b@gmail.com> (raw)
In-Reply-To: <87k08tfau0.fsf@gnu.org>
On 7/4/22 3:09 AM, Ludovic Courtès wrote:
> greed.
> I was wondering about offering an explicit ‘munmap’ interface: it would
> be useful for fine-grain OS resource management, just like ‘close-fdes’.
>
Sorry, missed the munmap.
scheme@(guile-user)> ,d munmap
- Scheme Procedure: munmap bvec
See the man page. Given bytevector generated by a mmap function,
unmap the associated memory. The argument will be modified to
reflect a zero length bv.
next prev parent reply other threads:[~2022-07-04 12:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 15:37 mmap for guile Matt Wette
2022-06-26 16:21 ` Matt Wette
2022-06-26 17:06 ` Olivier Dion via Developers list for Guile, the GNU extensibility library
2022-06-26 18:11 ` Maxime Devos
2022-07-04 10:09 ` Ludovic Courtès
2022-07-04 12:59 ` Matt Wette [this message]
2022-07-04 13:14 ` Greg Troxel
2022-07-04 20:03 ` Ludovic Courtès
2022-07-19 13:20 ` Maxime Devos
2022-07-21 9:14 ` Ludovic Courtès
2022-07-19 13:30 ` Maxime Devos
2022-07-19 13:34 ` Maxime Devos
2022-06-26 18:21 ` Maxime Devos
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5e2f37dc-58a4-817f-f088-593fddcdf95b@gmail.com \
--to=matt.wette@gmail.com \
--cc=guile-user@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).