From: Hugh Dickins <hugh@veritas.com>
To: Brent Casavant <bcasavan@sgi.com>
Cc: linux-mm@kvack.org
Subject: Re: [PATCH] /dev/zero page fault scaling
Date: Wed, 14 Jul 2004 21:39:39 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.44.0407142129090.2153-100000@localhost.localdomain> (raw)
In-Reply-To: <Pine.SGI.4.58.0407141418280.115007@kzerza.americas.sgi.com>
On Wed, 14 Jul 2004, Brent Casavant wrote:
>
> In a test program to measure the page fault performance, at 256P we
> see a 150x improvement in the number of page faults per cpu per
> wall-clock second (and other similar measures). Page fault performance
> drops by about 50% at 512P compared to 256P, however this is likely
> a seperate problem (investigation has not started), but is still
> 138x better than before these changes.
Wow. Good work.
> I'm not sure if this list is the appropriate place to submit these
> changes. If not, please direct me to the correct lists/people to
> submit this to. The patch is against 2.6.(something recent, maybe 7).
This list'll do fine. I'm the (unlisted) tmpfs maintainer, I'll give
your patch a go tomorrow, and try to convert it to NULL sbinfo as I
mentioned. I'll send you back the result, but won't send it on to
Andrew thence Linus for a couple of weeks, until after the Ottawa
Linux Symposium.
Thanks a lot!
Hugh
--
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:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-07-14 20:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-14 19:27 Brent Casavant
2004-07-14 20:39 ` Hugh Dickins [this message]
2004-07-14 21:31 ` Brent Casavant
2004-07-15 16:28 ` Brent Casavant
2004-07-15 20:28 ` Hugh Dickins
2004-07-15 21:36 ` Brent Casavant
2004-07-15 21:52 ` Brent Casavant
2004-07-15 23:21 ` Hugh Dickins
2004-07-16 22:35 ` Brent Casavant
2004-08-02 14:37 ` Brent Casavant
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=Pine.LNX.4.44.0407142129090.2153-100000@localhost.localdomain \
--to=hugh@veritas.com \
--cc=bcasavan@sgi.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox