From: ches@cheswick.com (William Cheswick)
Subject: [TUHS] History repeating itself (was: Unix v6 problem with /tmp)
Date: Sat, 30 Jul 2016 07:41:39 -0400 [thread overview]
Message-ID: <AE8CA14F-7551-4618-80C7-835832DBD4B1@cheswick.com> (raw)
In-Reply-To: <20160730075641.GT78278@eureka.lemis.com>
> On 30Jul 2016, at 3:56 AM, Greg 'groggy' Lehey <grog at lemis.com> wrote:
>
> Take that on a 20 minute drive, and you end up with a link bandwidth
> of about 22 Pb/s.
Of course, those cards take time to fill and empty, which should be part of the bandwidth
computation.
I was astonished to learn that one of those pinky-sized micro-SD cards has 33 circuit boards
in it, stacked in a staggered formation. 32 have memory, one a fairly powerful CPU.
next prev parent reply other threads:[~2016-07-30 11:41 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 20:28 [TUHS] Unix v6 problem with /tmp Mark Longridge
2016-07-27 20:31 ` William Pechter
2016-07-27 20:57 ` Clem Cole
2016-07-27 21:01 ` Clem Cole
2016-07-27 21:10 ` William Pechter
2016-07-28 0:49 ` Clem cole
2016-07-28 1:03 ` William Pechter
2016-07-28 11:23 ` [TUHS] History repeating itself (was: Unix v6 problem with /tmp) Michael Kjörling
2016-07-28 12:18 ` Tony Finch
2016-07-28 13:57 ` John Cowan
2016-07-30 7:56 ` Greg 'groggy' Lehey
2016-07-30 11:41 ` William Cheswick [this message]
2016-07-30 23:28 ` Greg 'groggy' Lehey
2016-07-30 23:50 ` scj
2016-08-01 11:36 ` Tony Finch
2016-07-30 14:15 ` John Cowan
2016-07-30 15:30 ` [TUHS] History repeating itself Michael Kjörling
2016-07-28 1:03 ` [TUHS] Unix v6 problem with /tmp Clem cole
2016-07-28 23:16 ` [TUHS] environments/universes (was: Unix v6 problem with /tmp) Sven Mascheck
2016-07-29 3:05 ` arnold
2016-07-29 14:14 ` Clem Cole
2016-07-29 13:55 ` Clem Cole
2016-07-31 4:25 [TUHS] History repeating itself " Rudi Blom
2016-08-01 1:08 ` John Cowan
2016-08-01 7:14 ` Rudi Blom
2016-08-01 17:11 ` scj
2016-08-01 18:32 ` Clem Cole
2016-08-02 22:38 ` Dave Horsfall
2016-08-03 11:53 Norman Wilson
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=AE8CA14F-7551-4618-80C7-835832DBD4B1@cheswick.com \
--to=ches@cheswick.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).