From: Rik van Riel <riel@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mel Gorman <mel@skynet.ie>, protasnb@gmail.com, linux-mm@kvack.org
Subject: Re: bug #5493
Date: Thu, 8 Nov 2007 13:15:18 -0500 [thread overview]
Message-ID: <20071108131518.5408931d@bree.surriel.com> (raw)
In-Reply-To: <20071108095704.f98905ec.akpm@linux-foundation.org>
On Thu, 8 Nov 2007 09:57:04 -0800
Andrew Morton <akpm@linux-foundation.org> wrote:
> > On Thu, 8 Nov 2007 16:53:20 +0000 mel@skynet.ie (Mel Gorman) wrote:
> > On (07/11/07 19:12), Andrew Morton didst pronounce:
> > > (added linux-mm)
> > >
> > > > On Wed, 7 Nov 2007 18:00:20 -0800 "Natalie Protasevich" <protasnb@gmail.com> wrote:
> > > > Andrew, this one http://bugzilla.kernel.org/show_bug.cgi?id=5493 looks
> > > > serious, and I'm not sure who to ping now that the reporter can't test
> > > > it anymore.
> > > > This is about mprotect ...
> > >
> > > No, I don't think anyone knows how to fix that.
> > >
> > > Fortunately I'm only aware of the one person hitting this problem.
> > >
> >
> > I tried out the test program with 1GiB of memory. First, the program could
> > not even run unless mprotect was called again to make pages read-only a
> > second time - otherwise mprotect would report ENOMEM because VMAs were not
> > getting merged. That in itself was a little unexpected.
> >
> > After fixing that, I ran with varying number of pages and got the
> > following timings
> >
> > 300000: 68.36 seconds
> > 295000: 55.07 seconds
> > 290000: 41.79 seconds
> > 285000: 31.71 seconds
> > 280000: 22.92 seconds
> > 275000: 11.27 seconds
> > 270000: 5.60 seconds
> > 265000: 5.94 seconds
> > 260000: 5.77 seconds
> > 255000: 5.65 seconds
> > 250000: 5.53 seconds
> > 245000: 5.42 seconds
> > 240000: 5.31 seconds
> >
> > The system has about 250000 pages and around that mark it seemed fine in
> > terms of time-to-completion. Above that vmstat was showing high figures
> > for si/so which is not a major suprise as such.
>
> hm, I was able to reproduce it way back when it was first reported. See
> below.
>
>
> > If this only occurs on systems with large amounts of memory, could it be
> > a variation of the excessive page-scanning problem that Rik has been on
> > about?
>
> No, it was due to linear traversal of very long reverse-mapping lists
> (thousands of elements, irrc).
Traversal at pageout time, or at mprotect time?
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-11-08 18:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <32209efe0711071800v4bc0c62er7bc462f1891c9dcd@mail.gmail.com>
2007-11-08 3:12 ` Andrew Morton
2007-11-08 16:53 ` Mel Gorman
2007-11-08 17:57 ` Andrew Morton
2007-11-08 18:15 ` Rik van Riel [this message]
2007-11-08 18:56 ` Andrew Morton
2007-11-09 1:00 ` Rik van Riel
2007-11-09 4:27 ` Andrew Morton
2007-11-09 4:52 ` Natalie Protasevich
2007-11-09 15:09 ` Rik van Riel
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=20071108131518.5408931d@bree.surriel.com \
--to=riel@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=mel@skynet.ie \
--cc=protasnb@gmail.com \
/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