From: "Mitchell, Earl" <earlm@mips.com>
To: "Wolfgang Denk" <wd@denx.de>, "Kevin D. Kissell" <kevink@mips.com>
Cc: "Sathesh Babu Edara" <satheshbabu.edara@analog.com>,
<linux-mips@linux-mips.org>
Subject: RE: [processor frequency]
Date: Mon, 9 Jan 2006 14:00:50 -0800 [thread overview]
Message-ID: <3CB54817FDF733459B230DD27C690CEC010495E3@Exchange.MIPS.COM> (raw)
Wolfgang,
In your summary you mention ...
"This probably explains why many developers who never use low-end embedded processors don't care about (and usually don't even know of) these problems in the 2.6 kernel."
The desktop/server guys typically use much larger caches (i.e. >= 512K)
and most have L2, compared to embedded systems which typically use less
without an L2. So I'd also expect embedded guys using small caches to see
larger decreases in performance due to more cache misses (i.e. more
interrupts produce more evictions).
-earlm
> -----Original Message-----
> From: linux-mips-bounce@linux-mips.org
> [mailto:linux-mips-bounce@linux-mips.org]On Behalf Of Wolfgang Denk
> Sent: Monday, January 09, 2006 1:24 PM
> To: Kevin D. Kissell
> Cc: Sathesh Babu Edara; linux-mips@linux-mips.org
> Subject: Re: [processor frequency]
>
>
> In message <005a01c614fb$2fe76b00$10eca8c0@grendel> you wrote:
> > There is no "ideal" value for a given processor frequency.
> > The lower the value, the less interrupt processing overhead,
> > but the slower the response time to events that are detected
> > or serviced during clock interrupts. 1000 HZ *may* be a sensible
> > value (I have my doubts, personally) for 2+ GHz PC processors,
> > but it's excessive (IMHO) for a 200MHz processor and unworkable
> > for a 20MHz CPU. I think that 100HZ is still a reasonable value
> > for an embedded RISC CPU, but the "ideal" value is going to
> > be a function of the application.
>
> We did some tests of the performance impact of 100 vs. 1000 Hz clock
> frequency on low end systems (50 MHz PowerPC); for details please see
> http://www.denx.de/wiki/view/Know/Clock100vs1000Hz
>
> Best regards,
>
> Wolfgang Denk
>
> --
> Software Engineering: Embedded and Realtime Systems, Embedded Linux
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
> Our missions are peaceful -- not for conquest. When we do battle, it
> is only because we have no choice.
> -- Kirk, "The Squire of Gothos", stardate 2124.5
>
>
WARNING: multiple messages have this Message-ID (diff)
From: "Mitchell, Earl" <earlm@mips.com>
To: Wolfgang Denk <wd@denx.de>, "Kevin D. Kissell" <kevink@mips.com>
Cc: Sathesh Babu Edara <satheshbabu.edara@analog.com>,
linux-mips@linux-mips.org
Subject: RE: [processor frequency]
Date: Mon, 9 Jan 2006 14:00:50 -0800 [thread overview]
Message-ID: <3CB54817FDF733459B230DD27C690CEC010495E3@Exchange.MIPS.COM> (raw)
Message-ID: <20060109220050.F1g_tyUXE4NahE8zEkWLRhcefBzY-Z7-V5FiK-4FGdA@z> (raw)
Wolfgang,
In your summary you mention ...
"This probably explains why many developers who never use low-end embedded processors don't care about (and usually don't even know of) these problems in the 2.6 kernel."
The desktop/server guys typically use much larger caches (i.e. >= 512K)
and most have L2, compared to embedded systems which typically use less
without an L2. So I'd also expect embedded guys using small caches to see
larger decreases in performance due to more cache misses (i.e. more
interrupts produce more evictions).
-earlm
> -----Original Message-----
> From: linux-mips-bounce@linux-mips.org
> [mailto:linux-mips-bounce@linux-mips.org]On Behalf Of Wolfgang Denk
> Sent: Monday, January 09, 2006 1:24 PM
> To: Kevin D. Kissell
> Cc: Sathesh Babu Edara; linux-mips@linux-mips.org
> Subject: Re: [processor frequency]
>
>
> In message <005a01c614fb$2fe76b00$10eca8c0@grendel> you wrote:
> > There is no "ideal" value for a given processor frequency.
> > The lower the value, the less interrupt processing overhead,
> > but the slower the response time to events that are detected
> > or serviced during clock interrupts. 1000 HZ *may* be a sensible
> > value (I have my doubts, personally) for 2+ GHz PC processors,
> > but it's excessive (IMHO) for a 200MHz processor and unworkable
> > for a 20MHz CPU. I think that 100HZ is still a reasonable value
> > for an embedded RISC CPU, but the "ideal" value is going to
> > be a function of the application.
>
> We did some tests of the performance impact of 100 vs. 1000 Hz clock
> frequency on low end systems (50 MHz PowerPC); for details please see
> http://www.denx.de/wiki/view/Know/Clock100vs1000Hz
>
> Best regards,
>
> Wolfgang Denk
>
> --
> Software Engineering: Embedded and Realtime Systems, Embedded Linux
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
> Our missions are peaceful -- not for conquest. When we do battle, it
> is only because we have no choice.
> -- Kirk, "The Squire of Gothos", stardate 2124.5
>
>
next reply other threads:[~2006-01-09 21:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 22:00 Mitchell, Earl [this message]
2006-01-09 22:00 ` [processor frequency] Mitchell, Earl
2006-01-09 23:05 ` Wolfgang Denk
2006-01-10 9:36 ` Dominic Sweetman
2006-01-10 9:36 ` Dominic Sweetman
-- strict thread matches above, loose matches on Subject: below --
2006-01-09 9:00 Kevin D. Kissell
2006-01-09 21:23 ` [processor frequency] Wolfgang Denk
2006-01-09 21:53 ` Kevin D. Kissell
2006-01-09 23:01 ` Wolfgang Denk
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=3CB54817FDF733459B230DD27C690CEC010495E3@Exchange.MIPS.COM \
--to=earlm@mips.com \
--cc=kevink@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=satheshbabu.edara@analog.com \
--cc=wd@denx.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 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.