tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: tech@mdocml.bsd.lv
Subject: Re: OSX + mmap + mansearch.c + documentation
Date: Sat, 9 Aug 2014 17:04:03 +0200	[thread overview]
Message-ID: <20140809150403.GB30999@iris.usta.de> (raw)
In-Reply-To: <53E60B48.5000003@bsd.lv>

Hi Kristaps,

Kristaps Dzonsons wrote on Sat, Aug 09, 2014 at 01:51:36PM +0200:

> 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.

Fixed in rc3.

That release candidate contains another fix for an issue
reported by Thomas Klausner:  config.h was forgotten in
mansearch_const.c.

> 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.)

Well, even on OpenBSD the manual says that either MAP_PRIVATE or
MAP_SHARED is required, it just doesn't seem to be enforced by the
implementation, so i simply added MAP_SHARED like in all
three other places where we use mmap(2), for minimum disruption
for the release.

Now i do wonder why we use MAP_SHARED and not MAP_PRIVATE.
But that's a question for after release, i have taken a note
in the TODO file.

> In general, the section scares me--I vaguely guess at what's
> happening, but have no idea why.

Unfortunately, at one point, i accidentally deleted my gprof(1)
logs, but off the top of my head, i'm quite sure the point was
that without SQLITE_CONFIG_PAGECACHE, apropos(1) spends
considerable extra time, that is, about 10-25% of the total
time it needs, in malloc(3) and free(3) called from within
sqlite3_*() functions.

> 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.

It scares you - you mean tedu@ might suspect exploit mitigation
countermeasures?  That might be worth investigating, too.
While espie@ holds the chief SQLite developer in high esteem,
deraadt@ hates the code quality.  Myself, i didn't form an
opinion on the SQLite code, yet.

But for this release, i'll keep the lid on that can of worms.

Yours,
  Ingo
--
 To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv

  reply	other threads:[~2014-08-09 15:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-09 11:51 Kristaps Dzonsons
2014-08-09 15:04 ` Ingo Schwarze [this message]
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=20140809150403.GB30999@iris.usta.de \
    --to=schwarze@usta.de \
    --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).