From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: Known problems with dcache?
Date: Fri, 10 Jan 2003 23:21:00 -0000 [thread overview]
Message-ID: <20030110232212.GA307@nevyn.them.org> (raw)
In-Reply-To: <3E1F542B.9060700@redhat.com>
On Fri, Jan 10, 2003 at 06:15:55PM -0500, Andrew Cagney wrote:
>
> >>Was it on an i386? If it was, the other other cache would easily skew
> >>any results.
> >
> >
> >Other other cache? Codestream doesn't affect this so I don't know what
> >you mean.
>
> It definitly affects things. Both codestream and dcache are chewing cpu
> cycles trying to cache instruction reads. A valid comparison would at
> least involve no dcache/codestream.
Sure; but it's overwhelmed by the LinuxThreads I/O, which doesn't touch
codestream at all; instruction reads weren't even a measurable time
last time I did this.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-01-10 23:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 22:19 Andrew Cagney
2003-01-10 22:25 ` Daniel Jacobowitz
2003-01-10 22:36 ` Andrew Cagney
2003-01-10 22:38 ` Daniel Jacobowitz
2003-01-10 22:55 ` Andrew Cagney
2003-01-10 23:04 ` Daniel Jacobowitz
2003-01-10 23:16 ` Andrew Cagney
2003-01-10 23:21 ` Daniel Jacobowitz [this message]
2003-01-11 17:52 ` Andrew Cagney
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=20030110232212.GA307@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.com \
--cc=gdb@sources.redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox