All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: Andrew Sharp <andy@netfall.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Measuring kernel compile times on smp system.
Date: Fri, 28 Oct 2005 10:08:19 +0800	[thread overview]
Message-ID: <43618813.9060804@tausq.org> (raw)
In-Reply-To: <20051027201333.GA3107@netfall.com>

> To really understand these numbers, you need three things: the amount
> of memory on the system, the L2 (and L3?) cache sizes,

http://en.wikipedia.org/wiki/PA-RISC

"An interesting aspect of the PA-RISC line is that most of its
generations have no Level 2 cache. Instead large Level 1 caches are
used, formerly as separate chips connected by a bus, now integrated
on-chip. Only the PA-7100LC and PA-7300LC had L2 caches."

randolph
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

       reply	other threads:[~2005-10-28  2:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1130389617.31977.16.camel@localhost.localdomain>
     [not found] ` <20051027201333.GA3107@netfall.com>
2005-10-28  2:08   ` Randolph Chung [this message]
2005-10-28  3:19     ` [parisc-linux] Measuring kernel compile times on smp system Matthew Wilcox
     [not found]   ` <1130543952.20233.10.camel@localhost.localdomain>
     [not found]     ` <1130563229.20233.19.camel@localhost.localdomain>
     [not found]       ` <4363E43D.5030208@tiscali.be>
     [not found]         ` <20051029214456.GB6550@parisc-linux.org>
     [not found]           ` <4363FBD4.9000003@tiscali.be>
     [not found]             ` <20051030000253.GA11807@colo.lackof.org>
2005-10-30 15:25               ` [parisc-linux] Question about ccio and fdc request: Matthew Wilcox
2005-10-28  2:55 ` [parisc-linux] Measuring kernel compile times on smp system James Bottomley

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=43618813.9060804@tausq.org \
    --to=randolph@tausq.org \
    --cc=andy@netfall.com \
    --cc=parisc-linux@lists.parisc-linux.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.