The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: Larry McVoy <lm@mcvoy.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] PDP-11 legacy, C, and modern architectures
Date: Thu, 28 Jun 2018 09:07:28 -0600	[thread overview]
Message-ID: <CANCZdfqXjhssV+CqDLvY_fxeRm0zdFt0YwRHMDzYdD2XRjbAWg@mail.gmail.com> (raw)
In-Reply-To: <20180628145609.GD21688@mcvoy.com>

[-- Attachment #1: Type: text/plain, Size: 1984 bytes --]

On Thu, Jun 28, 2018 at 8:56 AM, Larry McVoy <lm@mcvoy.com> wrote:

> On Thu, Jun 28, 2018 at 10:43:29AM -0400, Perry E. Metzger wrote:
> > On Thu, 28 Jun 2018 10:15:38 -0400 "Theodore Y. Ts'o" <tytso@mit.edu>
> > wrote:
> > > I'll note that Sun made a big bet (one of its last failed bets) on
> > > this architecture in the form of the Niagra architecture, with a
> > > large number of super "wimpy" cores.  It was the same basic idea
> > > --- we can't make big fast cores (since that would lead to high
> > > ILP's, complex register rewriting, and lead to cache-oriented
> > > security vulnerabilities like Spectre and Meltdown) --- so instead,
> > > let's make lots of tiny wimpy cores, and let programmers write
> > > highly threaded programs!  They essentially made a bet on the
> > > web-based microservice model which you are promoting.
> > >
> > > And the Market spoke.  And shortly thereafter, Java fell under the
> > > control of Oracle....  And Intel would proceed to further dominate
> > > the landscape.
> >
> > I'll be contrary for a moment.
> >
> > Huge numbers of wimpy cores is the model already dominating the
> > world.
>
> Got a source that backs up that claim?  I was recently dancing with
> Netflix and they don't match your claim, nor do the other content
> delivery networks, they want every cycle they can get.
>

Well, we want to be able to manage 100G or more of encrypted traffic sanely.

We currently get this by lots (well 20) of not-so-wimpy cores to do all the
work since none of the offload solutions can scale.

The problem is that there's no systems with lots (100's) of wimpy cores
that we can do the offload with that also have enough bandwidth to keep up.
And even if there were, things like NUMA and slow interprocessor connects
make the usefulness of the boatloads of cores a lot trickier to utilize
than it should....

Then again, a lot of what we do is rather special case, even if we do use
off the shelf technology to get there...

Warner

[-- Attachment #2: Type: text/html, Size: 2862 bytes --]

  reply	other threads:[~2018-06-28 15:07 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
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 [this message]
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=CANCZdfqXjhssV+CqDLvY_fxeRm0zdFt0YwRHMDzYdD2XRjbAWg@mail.gmail.com \
    --to=imp@bsdimp.com \
    --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).