From: "Nakajima, Jun" <jun.nakajima@intel.com>
To: igor@txc.com, linux-kernel@vger.kernel.org
Subject: RE: performance of cache-intensive applications
Date: Tue, 3 Dec 2002 18:17:52 -0800 [thread overview]
Message-ID: <F2DBA543B89AD51184B600508B68D4001070F20F@fmsmsx103.fm.intel.com> (raw)
This kind of problem could be solved by cache coloring. There should be some
patch available for Linux. I don't know if the other OSes you tried
implement cache coloring, though.
Jun
> -----Original Message-----
> From: Igor Schein [mailto:igor@txc.com]
> Sent: Tuesday, December 03, 2002 6:09 PM
> To: linux-kernel@vger.kernel.org
> Subject: performance of cache-intensive applications
>
> Hi,
>
> I am using an open-source application on ix86 to perform a task which
> is cache-intensive. When I run consecutive iterations of the task on
> a fixed input, the variance in timing of each iteration is extemely
> high. Needless to say, the test machine is always non-occupied.
>
> On every other OS I tried, Solaris, HPUX, FreeBSD and Tru64, the
> timing is very consistent between the iterations. My question is, are
> there known issues with L2 cache reuse in Linux kernel?
>
> I can provide any necessary information for anyone interested in
> addressing this issue, but I purposely skipped most technical details
> in this post to keep it simple.
>
> Thanks in advance.
>
> Igor
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2002-12-04 2:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-04 2:17 Nakajima, Jun [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-04 2:08 Igor Schein
2002-12-04 8:56 ` Giuliano Pochini
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=F2DBA543B89AD51184B600508B68D4001070F20F@fmsmsx103.fm.intel.com \
--to=jun.nakajima@intel.com \
--cc=igor@txc.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®