From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] PCIe x1 or PCIe x4 SATA controller card
Date: Mon, 27 Mar 2023 07:33:13 -0400 [thread overview]
Message-ID: <CAGfcS_=4qVQ+yGV6demm-nZTJiaE7Na5s3F-4_3LLoCi7AvXKw@mail.gmail.com> (raw)
In-Reply-To: <2b28be5d-0715-2633-3856-bd668a2758f4@youngman.org.uk>
On Mon, Mar 27, 2023 at 5:30 AM Wols Lists <antlists@youngman.org.uk> wrote:
>
> On 27/03/2023 01:18, Dale wrote:
> > Thanks for any light you can shed on this. Googling just leads to a ton
> > of confusion. What's true 6 months ago is wrong today. :/ It's hard
> > to tell what still applies.
>
> Well, back in the days of the megahurtz wars, a higher clock speed
> allegedly meant a faster CPU. Now they all run about 5GHz, and anything
> faster would break the speed of light ... so how they do it nowadays I
> really don't know ...
Effective instructions per clock in general, and increasing core count
are some of the big ones. I say effective because I think IPC is
somewhat synthetic and idealized, and there are MANY bottlenecks in a
CPU.
Efficiency improvements that allow a CPU to boost for longer or
increase sustained clock speed also help.
Getting more done in a clock cycle can happen in many ways:
1. Actually reducing the number of cycles needed to complete an
instruction at the most elementary level.
2. Using speculative execution to increase the number of instructions
run in parallel.
3. Improving branch prediction to maximize your speculative execution budget.
4. Reducing the cost of prediction errors by reducing pipelines/etc.
5. Better cache to reduce wait time.
6. Better internal IO to reduce wait time.
7. Better external IO (esp RAM) to reduce wait time.
Those are just ones I've thought of offhand. I'm sure there are tons
of info on which ones matter the most in practice, and things I
haven't thought of.
--
Rich
next prev parent reply other threads:[~2023-03-27 11:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 12:24 [gentoo-user] PCIe x1 or PCIe x4 SATA controller card Dale
2023-03-13 12:48 ` Rich Freeman
2023-03-13 14:34 ` Dale
2023-03-13 15:10 ` Mark Knecht
2023-03-15 12:45 ` Dale
2023-03-15 22:03 ` Frank Steinmetzger
2023-03-15 22:15 ` Frank Steinmetzger
2023-03-15 22:36 ` [gentoo-user]Computer build, was " Dale
2023-03-16 10:01 ` Frank Steinmetzger
2023-03-16 11:41 ` Rich Freeman
2023-03-26 19:08 ` [gentoo-user] " Dale
2023-03-26 21:21 ` Peter Humphrey
2023-03-26 23:21 ` Frank Steinmetzger
2023-03-27 0:18 ` Dale
2023-03-27 9:30 ` Wols Lists
2023-03-27 11:33 ` Rich Freeman [this message]
2023-03-27 10:37 ` Frank Steinmetzger
2023-03-27 11:24 ` Rich Freeman
2023-03-27 12:54 ` Frank Steinmetzger
2023-03-27 13:31 ` Wol
2023-03-27 13:45 ` Peter Humphrey
2023-09-19 13:40 ` Peter Humphrey
2023-09-20 0:51 ` Peter Humphrey
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='CAGfcS_=4qVQ+yGV6demm-nZTJiaE7Na5s3F-4_3LLoCi7AvXKw@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-user@lists.gentoo.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