From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Hugh Dickins <hugh@veritas.com>
Cc: Robin Holt <holt@sgi.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: munmap extremely slow even with untouched mapping.
Date: Sun, 30 Oct 2005 15:29:22 +1100 [thread overview]
Message-ID: <43644C22.8050501@yahoo.com.au> (raw)
In-Reply-To: <Pine.LNX.4.61.0510281557440.3229@goblin.wat.veritas.com>
Hugh Dickins wrote:
> Yes, it's a good observation from Robin.
>
> It'll have been spoiling the exit speedup we expected from your
> 2.6.14 copy_page_range "Don't copy [faultable] ptes" fork speedup.
>
Yep. Not to mention it is probably responsible for some of the
4 level page table performance slowdowns on x86-64.
>
>
> I prefer your patch too. But I'm not very interested in temporary
> speedups relative to 2.6.14. Attacking this is a job I'd put off
> until after the page fault scalability changes, which make it much
> easier to do a proper job.
>
Yeah definitely.
I wonder if we should go with Robin's fix (+/- my variation)
as a temporary measure for 2.6.15?
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
WARNING: multiple messages have this Message-ID (diff)
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Hugh Dickins <hugh@veritas.com>
Cc: Robin Holt <holt@sgi.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: munmap extremely slow even with untouched mapping.
Date: Sun, 30 Oct 2005 15:29:22 +1100 [thread overview]
Message-ID: <43644C22.8050501@yahoo.com.au> (raw)
In-Reply-To: <Pine.LNX.4.61.0510281557440.3229@goblin.wat.veritas.com>
Hugh Dickins wrote:
> Yes, it's a good observation from Robin.
>
> It'll have been spoiling the exit speedup we expected from your
> 2.6.14 copy_page_range "Don't copy [faultable] ptes" fork speedup.
>
Yep. Not to mention it is probably responsible for some of the
4 level page table performance slowdowns on x86-64.
>
>
> I prefer your patch too. But I'm not very interested in temporary
> speedups relative to 2.6.14. Attacking this is a job I'd put off
> until after the page fault scalability changes, which make it much
> easier to do a proper job.
>
Yeah definitely.
I wonder if we should go with Robin's fix (+/- my variation)
as a temporary measure for 2.6.15?
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
--
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:[~2005-10-30 4:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-28 1:37 munmap extremely slow even with untouched mapping Robin Holt
2005-10-28 1:37 ` Robin Holt
2005-10-28 10:45 ` Nick Piggin
2005-10-28 15:20 ` Hugh Dickins
2005-10-28 15:20 ` Hugh Dickins
2005-10-30 4:29 ` Nick Piggin [this message]
2005-10-30 4:29 ` Nick Piggin
2005-10-30 16:58 ` Hugh Dickins
2005-10-30 16:58 ` Hugh Dickins
2005-10-31 9:10 ` Nick Piggin
2005-10-31 9:19 ` Nick Piggin
2005-10-31 9:19 ` Nick Piggin
2005-10-31 12:20 ` Robin Holt
2005-10-31 12:20 ` Robin Holt
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=43644C22.8050501@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=holt@sgi.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.