From: Jon Masters <jonathan@jonmasters.org>
To: Steven Scholz <steven.scholz@imc-berlin.de>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: uncached user space mapping with mmap() ???
Date: Fri, 05 Mar 2004 11:35:28 +0000 [thread overview]
Message-ID: <40486600.9090304@jonmasters.org> (raw)
In-Reply-To: <404837D3.3060609@imc-berlin.de>
Steven Scholz wrote:
| Is it always better to map only the small part I am going to use?
Of course it is always best to map only the small range that you are
going to use and there will not necessarily be only one TLB mapping (I
am here referring to your comments on ARM Linux Kernel List) etc. etc.
However here especially I am inclined to repeat what they said on the
other list - these figures are so close that they might differ for other
reasons and so on. Did you repeat this in a controlled way many times?
You will need to answer the questions Russell King posted in order for
us to work through this and figure out where the difference lies.
Cheers,
Jon.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-03-05 11:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 13:51 uncached user space mapping with mmap() ??? Steven Scholz
2004-03-04 17:00 ` Dan Malek
2004-03-05 8:18 ` Steven Scholz
2004-03-05 11:35 ` Jon Masters [this message]
2004-03-05 11:41 ` Steven Scholz
2004-03-05 13:21 ` Jon Masters
-- strict thread matches above, loose matches on Subject: below --
2004-03-04 14:15 Fillod Stephane
2004-03-04 14:35 ` Steven Scholz
2004-03-04 17:28 ` Eugene Surovegin
2004-03-04 14:47 Fillod Stephane
2004-03-04 14:51 ` Steven Scholz
2004-03-04 23:02 Richard Williams
2004-03-04 23:17 ` Dan Malek
2004-03-08 10:25 Fillod Stephane
2004-03-09 10:55 ` Jon Masters
2004-03-09 12:49 Fillod Stephane
2004-03-12 12:07 ` Jon Masters
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=40486600.9090304@jonmasters.org \
--to=jonathan@jonmasters.org \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=steven.scholz@imc-berlin.de \
/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;
as well as URLs for NNTP newsgroup(s).