The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Larry McVoy <lm@mcvoy.com>
To: Norman Wilson <norman@oclsc.org>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Origins of the frame buffer device
Date: Mon, 6 Mar 2023 15:24:29 -0800	[thread overview]
Message-ID: <20230306232429.GL5398@mcvoy.com> (raw)
In-Reply-To: <8BD57BAB138946830AF560E17376A63B.for-standards-violators@oclsc.org>


On Mon, Mar 06, 2023 at 06:16:19PM -0500, Norman Wilson wrote:
> Rob Pike:
> 
>   As observed by many others, there is far more grunt today in the graphics
>   card than the CPU, which in Sutherland's timeline would mean it was time to
>   push that power back to the CPU. But no.
> 
> ====
> 
> Indeed.  Instead we are evolving ways to use graphics cards to
> do general-purpose computation, and assembling systems that have
> many graphics cards not to do graphics but to crunch numbers.
> 
> My current responsibilities include running a small stable of
> those, because certain computer-science courses consider it
> important that students learn to use them.
> 
> I sometimes wonder when someone will think of adding secondary
> storage and memory management and network interfaces to GPUs,
> and push to run Windows on them.

It's funny because back in my day those GPUs would have been called vector
processors, at least I think they would.  It seems like somewhere along
the way, vector processors became a dirty word but GPUS are fine.

Color me confused.

About the only reason I can see to keep things divided between the CPU
and the GPU is battery power, or power consumption in general.  From
what little I know, it seems like GPUs are pretty power thirsty so 
maybe they keep them as optional devices so people who don't need them
don't pay the power budget.

But even that seems suspect, I would think they could put some logic
in there that just doesn't feed power to the GPU if you aren't using
it but maybe that's harder than I think.

If it's not about power then I don't get it, there are tons of transistors
waiting to be used, they could easily plunk down a bunch of GPUs on the
same die so why not?  Maybe the dev timelines are completely different
(I suspect not, I'm just grabbing at straws).

  reply	other threads:[~2023-03-06 23:24 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-06 23:16 Norman Wilson
2023-03-06 23:24 ` Larry McVoy [this message]
2023-03-07 12:08   ` arnold
2023-03-07 16:42   ` Theodore Ts'o
  -- strict thread matches above, loose matches on Subject: below --
2023-03-05 18:52 Noel Chiappa
2023-03-05 20:43 ` Rob Pike
2023-03-06 10:43   ` Jonathan Gray
2023-03-07  1:21 ` Kenneth Goodwin
2023-03-08  5:43 ` Lars Brinkhoff
2023-03-09 23:24   ` emanuel stiebler
2023-03-10  1:44     ` Lawrence Stewart
2023-03-05 15:01 [TUHS] " Paul Ruizendaal via TUHS
2023-03-05 17:29 ` [TUHS] " Grant Taylor via TUHS
2023-03-05 18:25 ` Kenneth Goodwin
2023-03-06  8:51   ` Paul Ruizendaal via TUHS
2023-03-06  8:57     ` Rob Pike
2023-03-06 11:09       ` Henry Bent
2023-03-06 16:02         ` Theodore Ts'o
2023-03-06 22:47       ` Paul Ruizendaal via TUHS
2023-03-06 23:10         ` Rob Pike
2023-03-08 12:53           ` Paul Ruizendaal
2023-03-08 14:23             ` Dan Cross
2023-03-08 15:06               ` Paul Ruizendaal
2023-03-08 19:35                 ` Dan Cross
2023-03-08 16:55               ` Theodore Ts'o
2023-03-08 17:46                 ` Clem Cole
2023-03-08 17:45               ` Clem Cole
2023-03-08 18:12                 ` segaloco via TUHS
2023-03-08 18:21                   ` Larry McVoy
2023-03-08 18:43                     ` Kenneth Goodwin
2023-03-08 18:45                     ` Steffen Nurpmeso
2023-03-08 22:44                     ` Clem Cole
2023-03-09 14:42                 ` Paul Winalski
2023-03-06 23:20         ` segaloco via TUHS
2023-03-07  1:24     ` Kenneth Goodwin
2023-03-08  3:07     ` Rob Gingell
2023-03-08 12:51       ` Paul Ruizendaal via TUHS
2023-03-08 13:05         ` Warner Losh
2023-03-08 13:17         ` Arno Griffioen via TUHS
2023-03-07  1:54 ` Kenneth Goodwin

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=20230306232429.GL5398@mcvoy.com \
    --to=lm@mcvoy.com \
    --cc=norman@oclsc.org \
    --cc=tuhs@tuhs.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;
as well as URLs for NNTP newsgroup(s).