From: Kristaps Dzonsons <kristaps@bsd.lv>
To: tech@mdocml.bsd.lv
Subject: OSX + mmap + mansearch.c + documentation
Date: Sat, 09 Aug 2014 13:51:36 +0200 [thread overview]
Message-ID: <53E60B48.5000003@bsd.lv> (raw)
Hi,
Small thing noticed in OSX:
% /usr/local/bin/apropos find
mmap: Invalid argument
According to the Mac OSX manpage for mmap(2), this is because:
[EINVAL] flags does not include either MAP_PRIVATE or MAP_SHARED.
It's easy enough to add a mmap_flags variable as MAP_ANON | blah and
ifdef it to do one or the other. (I hesitate to say which, but am
guessing MAP_PRIVATE since the page cache isn't (???) shared across
processes.)
In general, the section scares me--I vaguely guess at what's happening,
but have no idea why. So more pertinently than the bit-field would be
to document this section! Ingo mentions the speed reduction in his talk
(pg. 20, http://www.openbsd.org/papers/bsdcan14-mandoc.pdf), but not
/why/ there's a speed reduction.
Best,
Kristaps
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
next reply other threads:[~2014-08-09 11:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-09 11:51 Kristaps Dzonsons [this message]
2014-08-09 15:04 ` Ingo Schwarze
2014-08-10 8:26 ` Kristaps Dzonsons
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=53E60B48.5000003@bsd.lv \
--to=kristaps@bsd.lv \
--cc=tech@mdocml.bsd.lv \
/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 NNTP newsgroup(s).