Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] Fwd: Will Edwards to give Mill talk in Estonia on 12/10/2014
Date: Wed, 10 Dec 2014 08:13:05 +0200	[thread overview]
Message-ID: <CAJq5cE3_mxmFzMwLLDv-qAVDyisJgr2ev_BE9rGUwR+RdnXcgw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4zMJGmoARkOqvZ2eapU7f5OoaF4hiTDJ-AMmP5x3dMzA@mail.gmail.com>

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

Watching all the talks takes more than just an hour, but I've just spent a
couple of days doing so. This is certainly intriguing. At first glance it
all looks too good to be true, but the technical details actually look
plausible and elegant.

One way to look at it is: Mill is what Itanic could have been, if it wasn't
designed by committee. It neatly sidesteps a lot of the pitfalls that tend
to go with VLIW designs, and therefore has a chance of actually working as
advertised, unlike Itanic.

The only thing that I'm really not convinced about is the way they produce
a custom instruction encoding for each member of the architecture family.
However, that does make the architecture scalable, unlike Itanic.

It's possible that some of the more useful ideas it presents could have
been incorporated into a conventional RISC architecture. I might play with
that idea privately.

Estonia is even quite close to where I am, just the opposite side of the
Gulf of Finland, so I'm almost tempted to go and take a look. On the other
hand, it's probably just as educational to watch the video at home
afterwards, and doing so avoids scheduling conflict.

- Jonathan Morton

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

      reply	other threads:[~2014-12-10  6:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <daeaa4982a7a1c6b864c6b557d27ac1acc3.20141205184544@mail158.atl21.rsgsv.net>
2014-12-05 19:18 ` [Cerowrt-devel] " Dave Taht
2014-12-05 19:33   ` Valdis.Kletnieks
2014-12-05 20:15     ` Dave Taht
2014-12-10  6:13       ` Jonathan Morton [this message]

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJq5cE3_mxmFzMwLLDv-qAVDyisJgr2ev_BE9rGUwR+RdnXcgw@mail.gmail.com \
    --to=chromatix99@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@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