From: Tim Bradshaw <tfb@tfeb.org>
To: Larry McVoy <lm@mcvoy.com>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] PDP-11 legacy, C, and modern architectures
Date: Thu, 28 Jun 2018 17:41:24 +0100 [thread overview]
Message-ID: <79022674-0FFA-4B1B-8A27-4C403D51540E@tfeb.org> (raw)
In-Reply-To: <20180628160202.GF21688@mcvoy.com>
On 28 Jun 2018, at 17:02, Larry McVoy <lm@mcvoy.com> wrote:
>
> But when you are doing real work, sorting
> the genome, machine learning, whatever, performance is a thing and
> lots of wimpy cpus are not.
But lots of (relatively) wimpy CPUs is what physics says you will have and you really can't argue with physics.
I think this is definitely off-topic now so I won't reply further: feel free to mail me privately.
next prev parent reply other threads:[~2018-06-28 16:41 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 17:54 Nelson H. F. Beebe
2018-06-26 18:03 ` Cornelius Keck
2018-06-26 21:21 ` Nelson H. F. Beebe
2018-06-26 21:56 ` Kurt H Maier
2018-06-26 18:52 ` Ronald Natalie
2018-06-26 19:01 ` Ronald Natalie
2018-06-26 21:16 ` Arthur Krewat
2018-06-26 21:50 ` Larry McVoy
2018-06-26 21:54 ` Ronald Natalie
2018-06-26 21:59 ` Larry McVoy
2018-06-26 22:20 ` Bakul Shah
2018-06-26 22:33 ` Arthur Krewat
2018-06-26 23:53 ` Bakul Shah
2018-06-27 8:30 ` Tim Bradshaw
2018-06-26 22:33 ` Andy Kosela
2018-06-27 0:11 ` Bakul Shah
2018-06-27 6:10 ` arnold
2018-06-27 2:18 ` [TUHS] PDP-11 legacy, C, and modern architectTures Theodore Y. Ts'o
2018-06-27 2:22 ` Theodore Y. Ts'o
2018-06-28 14:36 ` Steffen Nurpmeso
2018-06-27 11:26 ` [TUHS] PDP-11 legacy, C, and modern architectures Tony Finch
2018-06-27 14:33 ` Clem Cole
2018-06-27 14:38 ` Clem Cole
2018-06-27 15:30 ` Paul Winalski
2018-06-27 16:55 ` Tim Bradshaw
2018-06-27 6:27 ` arnold
2018-06-27 16:00 ` Steve Johnson
2018-06-28 4:12 ` Bakul Shah
2018-06-28 14:15 ` Theodore Y. Ts'o
2018-06-28 14:40 ` Larry McVoy
2018-06-28 14:55 ` Perry E. Metzger
2018-06-28 14:58 ` Larry McVoy
2018-06-28 15:39 ` Tim Bradshaw
2018-06-28 16:02 ` Larry McVoy
2018-06-28 16:41 ` Tim Bradshaw [this message]
2018-06-28 16:59 ` Paul Winalski
2018-06-28 17:09 ` Larry McVoy
2018-06-29 15:32 ` tfb
2018-06-29 16:09 ` Perry E. Metzger
2018-06-29 17:51 ` Larry McVoy
2018-06-29 18:27 ` Tim Bradshaw
2018-06-29 19:02 ` Perry E. Metzger
2018-06-28 20:37 ` Perry E. Metzger
2018-06-28 15:37 ` Clem Cole
2018-06-28 20:37 ` Lawrence Stewart
2018-06-28 14:43 ` Perry E. Metzger
2018-06-28 14:56 ` Larry McVoy
2018-06-28 15:07 ` Warner Losh
2018-06-28 19:42 ` Perry E. Metzger
2018-06-28 19:55 ` Paul Winalski
2018-06-28 20:42 ` Warner Losh
2018-06-28 21:03 ` Perry E. Metzger
2018-06-28 22:29 ` Theodore Y. Ts'o
2018-06-29 0:18 ` Larry McVoy
2018-06-29 15:41 ` Perry E. Metzger
2018-06-29 18:01 ` Larry McVoy
2018-06-29 19:07 ` Perry E. Metzger
2018-06-29 5:58 ` Michael Kjörling
2018-06-28 20:52 ` Lawrence Stewart
2018-06-28 21:07 ` Perry E. Metzger
2018-06-28 16:45 ` Paul Winalski
2018-06-28 20:47 ` Perry E. Metzger
2018-06-29 15:43 ` emanuel stiebler
2018-06-29 2:02 ` Bakul Shah
2018-06-29 12:58 ` Theodore Y. Ts'o
2018-06-29 18:41 ` Perry E. Metzger
2018-06-29 1:02 Noel Chiappa
2018-06-29 1:06 Noel Chiappa
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=79022674-0FFA-4B1B-8A27-4C403D51540E@tfeb.org \
--to=tfb@tfeb.org \
--cc=lm@mcvoy.com \
--cc=tuhs@minnie.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).