From: John Cowan <cowan@ccil.org>
To: Dan Cross <crossd@gmail.com>
Cc: ron minnich <rminnich@gmail.com>, COFF <coff@tuhs.org>
Subject: [COFF] Re: [TUHS] Re: the wheel of reincarnation goes sideways
Date: Wed, 8 Mar 2023 20:22:39 -0500 [thread overview]
Message-ID: <CAD2gp_R=uqX4VidxTik8d1L-KYSsp4KwdMSFXx2kJdrCJ6ojbQ@mail.gmail.com> (raw)
In-Reply-To: <CAEoi9W4nMjhXvv0zeQViWwuR=PYN7eJCto_Y8W_VRqzfM0-p7w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 936 bytes --]
On Wed, Mar 8, 2023 at 2:53 PM Dan Cross <crossd@gmail.com> wrote:
> > Now I'm seeing it in peripheral devices that have, not one, but several
> independent SoCs, all running Linux, on one card. There's even been a
> recent remote code exploit on, ... an LCD panel.
>
I remember at one time I had on my desk a PC with an 80x86 CPU and an
Ethernet card that had an 80(x+1)86 chip inside. I think x=0, but I'm not
sure.
> But the
> 3090 was really more like a distributed system than the Athlon box
> was, with all sorts of offload capabilities. For that matter, a
> thousand users probably _could_ telnet into the Athlon system. With
> telnet in line mode, it'd probably even be decently responsive.
>
I find that difficult to believe. It seems too high by an order of
magnitude. Another thing that doesn't get mentioned much is that classic
mainframes had SRAM, so their memory bandwidth was enormous.
[-- Attachment #2: Type: text/html, Size: 1910 bytes --]
next prev parent reply other threads:[~2023-03-09 1:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAP6exY+05fStBtpZGd2HeeNf21fNXeKUTwBV0h5-1YczwF+tew@mail.gmail.com>
2023-03-08 19:52 ` [COFF] Re: [TUHS] " Dan Cross
2023-03-08 20:18 ` [COFF] " Tom Ivar Helbekkmo via COFF
2023-03-09 1:22 ` John Cowan [this message]
2023-03-09 19:55 ` [COFF] Re: [TUHS] " Dan Cross
2023-03-09 20:09 ` Larry McVoy
2023-03-11 20:32 ` Dan Cross
2023-03-11 23:28 ` Bakul Shah
[not found] ` <ZA+gxAePDMWK6StD@straylight.ringlet.net>
2023-03-13 22:34 ` Dan Cross
2023-07-05 21:48 ` Dan Cross
2023-07-05 23:58 ` Grant Taylor via COFF
2023-07-06 1:02 ` Dave Horsfall
2023-07-06 16:47 ` Grant Taylor via COFF
2023-07-06 2:35 ` Dan Cross
2023-07-06 4:18 ` Robert Stanford via COFF
2023-07-06 16:53 ` Grant Taylor via COFF
2023-07-06 17:54 ` Adam Thornton
2023-07-09 14:55 ` Michael Parson
2023-08-01 9:52 ` Michael Cardell Widerkrantz
2023-08-01 9:49 ` Michael Cardell Widerkrantz
2023-08-01 15:55 ` Dan Cross
2023-08-01 16:27 ` Grant Taylor via COFF
2023-08-02 16:07 ` Dan Cross
2023-08-02 20:58 ` Grant Taylor via COFF
2023-08-02 21:16 ` Dan Cross
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='CAD2gp_R=uqX4VidxTik8d1L-KYSsp4KwdMSFXx2kJdrCJ6ojbQ@mail.gmail.com' \
--to=cowan@ccil.org \
--cc=coff@tuhs.org \
--cc=crossd@gmail.com \
--cc=rminnich@gmail.com \
/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).