From: Russell King <rmk@arm.linux.org.uk>
To: Jamie Lokier <lk@tantalophile.demon.co.uk>
Cc: David Woodhouse <dwmw2@infradead.org>,
Christoph Rohland <cr@sap.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Maciej Zenczykowski <maze@druid.if.uj.edu.pl>,
linux-kernel@vger.kernel.org
Subject: Re: [OT] Wrapping memory.
Date: Tue, 4 Dec 2001 21:03:38 +0000 [thread overview]
Message-ID: <20011204210338.C19783@flint.arm.linux.org.uk> (raw)
In-Reply-To: <m3r8qcagt7.fsf@linux.local> <E16AIZ8-0008Re-00@the-village.bc.nu> <12969.1007315617@redhat.com> <m3r8qcagt7.fsf@linux.local> <25163.1007370678@redhat.com> <20011204104047.A18147@flint.arm.linux.org.uk> <20011204163950.B28839@kushida.jlokier.co.uk>
In-Reply-To: <20011204163950.B28839@kushida.jlokier.co.uk>; from lk@tantalophile.demon.co.uk on Tue, Dec 04, 2001 at 04:39:50PM +0000
On Tue, Dec 04, 2001 at 04:39:50PM +0000, Jamie Lokier wrote:
> Unfortunately, the update_mmu_cache makes aliasing work properly while
> ruining performence, so then it's better to not to use the mapping trick
> at all in that case. To check for this, I have to call gettimeofday()
> between pairs of accesses, to check whether they are slow. I don't know
> for sure if this works because I don't have an ARM to try it on.
Why not create a program and email it to someone with an ARM machine?
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2001-12-04 21:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-01 22:03 [OT] Wrapping memory Maciej Zenczykowski
2001-12-01 22:24 ` Alan Cox
2001-12-02 1:52 ` Benjamin LaHaise
2001-12-02 10:24 ` Christoph Rohland
2001-12-02 17:53 ` David Woodhouse
2001-12-03 7:44 ` Christoph Rohland
2001-12-03 9:11 ` David Woodhouse
2001-12-04 10:40 ` Russell King
2001-12-04 16:39 ` Jamie Lokier
2001-12-04 21:03 ` Russell King [this message]
2001-12-04 10:45 ` David Woodhouse
2001-12-04 10:59 ` Russell King
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=20011204210338.C19783@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cr@sap.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lk@tantalophile.demon.co.uk \
--cc=maze@druid.if.uj.edu.pl \
/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.