From: Ralf Baechle <ralf@linux-mips.org>
To: Fuxin Zhang <fxzhang@ict.ac.cn>
Cc: linux-mips@linux-mips.org
Subject: Re: Cache code changes
Date: Thu, 20 Mar 2003 13:05:29 +0100 [thread overview]
Message-ID: <20030320130528.A15475@linux-mips.org> (raw)
In-Reply-To: <3E79A121.6000409@ict.ac.cn>; from fxzhang@ict.ac.cn on Thu, Mar 20, 2003 at 07:08:17PM +0800
On Thu, Mar 20, 2003 at 07:08:17PM +0800, Fuxin Zhang wrote:
> I am very glad to see this happens:)
> Currently linux/mips is really far from efficient,I've some data for
> this declaration:
> For most SPEC CPU 2000 programs we run on a 4-way superscalar CPU
> simulator
> ,we get <0.20 IPC in kernel mode,while the IPCs for the whole execution
> are often much
> higher(0.5-1.5). We believe this has something to do with the overly
> used cache flushes.
What type of cache are you using in this simulation? Virtual/physical
indexing/tagging, what associativity?
Linux/MIPS's handling of virtually indexed data caches isn't as good as
it should be but that's what I'm working on.
> BTW, for 2.4.17,it seems this path is still not safe for cache aliases:
> copy_cow_page for newly forked process, we use kernel virtual address
> to do the copy,but without flush first.
> add a flush_page_to_ram before the copy fix the errors.
>
> but i am not sure whether i am missing something
The functions clear_user_page and copy_user_page are supposed to take care
of aliases in this case. That's what the little patch did in my previous
mail did, just in a rather inefficient way.
Ralf
next prev parent reply other threads:[~2003-03-20 12:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-20 10:16 Cache code changes Ralf Baechle
2003-03-20 11:08 ` Fuxin Zhang
2003-03-20 12:05 ` Ralf Baechle [this message]
2003-03-21 11:53 ` Dominic Sweetman
2003-03-21 14:48 ` Juan Quintela
2003-03-31 12:01 ` Ralf Baechle
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=20030320130528.A15475@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=fxzhang@ict.ac.cn \
--cc=linux-mips@linux-mips.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.