[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <462C2F33.8090508@redhat.com>
Date: Sun, 22 Apr 2007 23:59:47 -0400
From: Rik van Riel <riel@...hat.com>
To: Rik van Riel <riel@...hat.com>
CC: Nick Piggin <nickpiggin@...oo.com.au>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-mm <linux-mm@...ck.org>, shak <dshaks@...hat.com>,
jakub@...hat.com, drepper@...hat.com
Subject: Re: [PATCH] lazy freeing of memory through MADV_FREE
Rik van Riel wrote:
> Nick Piggin wrote:
>> Rik van Riel wrote:
>>> Nick Piggin wrote:
>>>
>>>> Rik van Riel wrote:
>>
>>>>> Here are the transactions/seconds for each combination:
>
> I've added a 5th column, with just your mmap_sem patch and
> without my madv_free patch. It is run with the glibc patch,
> which should make it fall back to MADV_DONTNEED after the
> first MADV_FREE call fails.
>
>>>>> vanilla new glibc madv_free kernel madv_free + mmap_sem
>>>>> mmap_sem
>>>>> threads
>>>>>
>>>>> 1 610 609 596 545 534
>>>>> 2 1032 1136 1196 1200 1180
>>>>> 4 1070 1128 2014 2024 2027
>>>>> 8 1000 1088 1665 2087 2089
>>>>> 16 779 1073 1310 1999 2012
Now that I think about it - this is all with the rawhide kernel
configuration, which has an ungodly number of debug config
options enabled.
I should try this with a more normal kernel, on various different
systems.
It would also be helpful if other people tried this same benchmark,
and others, on their systems.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists