From: "David S. Miller" <davem@redhat.com>
To: davidm@hpl.hp.com
Cc: davidm@napali.hpl.hp.com, wli@holomorphy.com, torvalds@osdl.org,
linux-arch@vger.kernel.org
Subject: Re: copy_page_range()
Date: Mon, 9 Aug 2004 10:46:16 -0700 [thread overview]
Message-ID: <20040809104616.3ce07ddf.davem@redhat.com> (raw)
In-Reply-To: <16663.17268.247682.953102@napali.hpl.hp.com>
On Mon, 9 Aug 2004 02:27:16 -0700
David Mosberger <davidm@napali.hpl.hp.com> wrote:
> >>>>> On Mon, 9 Aug 2004 02:04:58 -0700, William Lee Irwin III <wli@holomorphy.com> said:
>
> William> These results are actually consistent with large-memory
> William> ia32. Instruction-level profiles showed that the largest
> William> overhead in copy_page_range() on such ia32 boxen appeared
> William> to be mm->rss++.
>
> Hmmh, for me, the single biggest stall seems to come from the pmd_none()
> check in free_one_pmd().
Right, that is what gets hit on sparc64 too.
On ia32, the tables are half the size, thus half the amount of
memory accesses per table traversal.
next prev parent reply other threads:[~2004-08-09 17:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-07 7:05 copy_page_range() David S. Miller
2004-08-07 8:07 ` copy_page_range() William Lee Irwin III
2004-08-11 7:07 ` copy_page_range() David S. Miller
2004-08-11 7:35 ` copy_page_range() William Lee Irwin III
2004-08-11 16:13 ` copy_page_range() Linus Torvalds
2004-08-11 20:45 ` copy_page_range() David S. Miller
2004-08-12 3:53 ` copy_page_range() David S. Miller
2004-08-09 9:01 ` copy_page_range() David Mosberger
2004-08-09 9:04 ` copy_page_range() William Lee Irwin III
2004-08-09 9:27 ` copy_page_range() David Mosberger
2004-08-09 9:29 ` copy_page_range() William Lee Irwin III
2004-08-09 10:01 ` copy_page_range() David Mosberger
2004-08-09 17:46 ` David S. Miller [this message]
2004-08-09 17:08 ` copy_page_range() Linus Torvalds
2004-08-09 18:49 ` copy_page_range() William Lee Irwin III
2004-08-09 17:45 ` copy_page_range() David S. Miller
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=20040809104616.3ce07ddf.davem@redhat.com \
--to=davem@redhat.com \
--cc=davidm@hpl.hp.com \
--cc=davidm@napali.hpl.hp.com \
--cc=linux-arch@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=wli@holomorphy.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 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.