Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] living in the future is fun
Date: Tue, 18 Mar 2014 19:16:36 -0700	[thread overview]
Message-ID: <CAA93jw4sNnU+DDKmDDbT5+jZUJjj7xqLFLncAqOfHj=2kfm=TQ@mail.gmail.com> (raw)

back in days of yore, power supplies were big, honking things,
requiring a fan and so on and were usually the most unreliable
part in a box.

Once, I was on a beach in Belize in 2002, and the hotel asked me to
see if I could fix a couple computers. I merely touched one of their
power supplies and the accumulated corrosion made it crumble away
in my hands...

Now the AC-DC conversion problem is in ever smaller sealed bricks,
and DC-DC conversions we  can do from a 12v supply is amazing.

PCs have complex voltage requirements, and I remember being
blown away a few (6?) years back when I saw my first solid state "pico"
DC-2-DC converter which did maybe 30 watts and was a bit
larger than this:

http://www.mini-box.com/picoPSU-160-XT

Battery life and power density have also improved dramatically,
3 axis accellerometers are cheap and plentiful, cpus run at ghz
speeds with multiple cores (the first embedded linux box I ever
built (1998) was a 25Mhz 486SX), and run on 10 watts or less,
wifi has gone from 2mbit to 1gbit, ethernet from a gigabit to 40gigE,
memory from megabytes to gigabytes, storage from spinning rust
to flash...

...and "acceptible" internet latency (for people other than us) is
still way above 100ms.



-- 

Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

                 reply	other threads:[~2014-03-19  2:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAA93jw4sNnU+DDKmDDbT5+jZUJjj7xqLFLncAqOfHj=2kfm=TQ@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /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