From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Rik van Riel <riel@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH] MM: implement MADV_FREE lazy freeing of anonymous memory
Date: Sat, 05 May 2007 09:47:56 +1000 [thread overview]
Message-ID: <463BC62C.3060605@yahoo.com.au> (raw)
In-Reply-To: <463B598B.80200@redhat.com>
Ulrich Drepper wrote:
> Nick Piggin wrote:
>
>>What I found is that, on this system, MADV_FREE performance improvement
>>was in the noise when you look at it on top of the MADV_DONTNEED glibc
>>and down_read(mmap_sem) patch in sysbench.
>
>
> I don't want to judge the numbers since I cannot but I want to make an
> observations: even if in the SMP case MADV_FREE turns out to not be a
> bigger boost then there is still the UP case to keep in mind where Rik
> measured a significant speed-up. As long as the SMP case isn't hurt
> this is reaosn enough to use the patch. With more and more cores on one
> processor SMP systems are pushed evermore to the high-end side. You'll
> find many installations which today use SMP will be happy enough with
> many-core UP machines.
OK, sure. I think we need more numbers though.
And even if this was a patch with _no_ possibility for regressions and it
was a completely trivial one that improves performance in some cases...
one big problem is that it uses another page flag.
I literally have about 4 or 5 new page flags I'd like to add today :) I
can't of course, because we have very few spare ones left.
From the MySQL numbers on this system, it seems like performance is in the
noise, and MADV_DONTNEED makes the _vast_ majority of the improvement.
This is also the case with Rik's benchmarks, and while he did see some
improvement, I found the runs to be quite variable, so it would be ideal
to get a larger sample.
And the fact that the poor behaviour of the old style malloc/free went
unnoticed for so long indicates that it won't be the end of the world if
we didn't merge MADV_FREE right now.
--
SUSE Labs, Novell Inc.
--
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-05-04 23:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-28 4:43 Rik van Riel
2007-05-04 10:53 ` Nick Piggin
2007-05-04 11:58 ` Rik van Riel
2007-05-04 23:49 ` Nick Piggin
2007-05-04 16:04 ` Ulrich Drepper
2007-05-04 23:47 ` Nick Piggin [this message]
2007-05-05 0:10 ` Ulrich Drepper
2007-05-06 22:43 ` Rik van Riel
2007-05-07 2:42 ` Ulrich Drepper
2007-05-07 4:56 ` Rik van Riel
2007-05-07 4:53 ` Ulrich Drepper
2007-05-07 16:51 ` Rik van Riel
2007-05-08 6:12 ` Nick Piggin
2007-05-08 14:59 ` Rik van Riel
2007-05-08 23:23 ` Nick Piggin
2007-05-08 18:35 ` Jakub Jelinek
2007-05-08 23:43 ` Nick Piggin
2007-05-08 3:51 ` [PATCH] stub MADV_FREE implementation Rik van Riel
2007-05-08 23:05 ` Andrew Morton
2007-05-09 17:15 ` Ulrich Drepper
2007-05-09 16:38 ` [PATCH] MM: implement MADV_FREE lazy freeing of anonymous memory Hugh Dickins
2007-05-29 16:59 ` 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=463BC62C.3060605@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@linux-foundation.org \
--cc=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
--cc=torvalds@linux-foundation.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