From: William Josephson <jkw@eecs.harvard.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] threads vs forks
Date: Sat, 7 Mar 2009 09:37:55 -0500 [thread overview]
Message-ID: <20090307143755.GB68357@mero.morphisms.net> (raw)
In-Reply-To: <6cbc566e63d124cdbc8191a6060c2e6f@quanstro.net>
On Sat, Mar 07, 2009 at 08:58:42AM -0500, erik quanstrom wrote:
> i think that's why they put them in a 2.5" form factor with a standard
> SATA interface. what are you thinking of?
No, the reason they do that is for backwards compatibility.
> > SSDs are expensive on a $/MB basis compared to disks. The good ones
>
> not as much as you think. a top-drawer 15k sas drive is on the order
> of 300GB and $350+. the intel ssd is only twice as much. if you compare
> the drives supported by the big-iron vendors, intel ssd already has cost
> parity.
The Intel SSD is cheap and slow :-)
> > For short-lived data you only need go over the I/O bus twice vs. three
> > times for most NVRAMs based on battery-backed DRAM.
>
> i'm missing something here. what are your assumptions
> on how things are connected? also, isn't there an assumption
> that you don't want to be writing short-lived data to flash if
> possible?
Take a gander at the NetApp NAS filers or DataDomain restorers.
Things have to go to NVRAM in case of a crash. The DRAM based
NVRAMs are typically quite a bit more expensive than flash
based ones and so you have less of it. That means more data
has to get flushed to disk since it can't live in battery-backed
NVRAM permanently.
next prev parent reply other threads:[~2009-03-07 14:37 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 11:52 hugo rivera
2009-03-03 15:19 ` David Leimbach
2009-03-03 15:32 ` Uriel
2009-03-03 16:15 ` hugo rivera
2009-03-03 15:33 ` hugo rivera
2009-03-03 18:11 ` Roman V. Shaposhnik
2009-03-03 18:38 ` Bakul Shah
2009-03-06 18:47 ` Roman V Shaposhnik
2009-03-06 20:38 ` David Leimbach
2009-03-07 8:00 ` Bakul Shah
2009-03-07 0:21 ` Bakul Shah
2009-03-07 2:20 ` Brian L. Stuart
2009-03-03 23:08 ` J.R. Mauro
2009-03-03 23:15 ` Uriel
2009-03-03 23:23 ` J.R. Mauro
2009-03-03 23:54 ` Devon H. O'Dell
2009-03-04 0:33 ` J.R. Mauro
2009-03-04 0:54 ` erik quanstrom
2009-03-04 1:54 ` J.R. Mauro
2009-03-04 3:18 ` James Tomaschke
2009-03-04 3:30 ` erik quanstrom
2009-03-04 4:44 ` James Tomaschke
2009-03-04 5:05 ` J.R. Mauro
2009-03-04 5:50 ` erik quanstrom
2009-03-04 6:08 ` andrey mirtchovski
2009-03-04 16:52 ` J.R. Mauro
2009-03-04 17:14 ` ron minnich
2009-03-04 17:27 ` William Josephson
2009-03-04 18:15 ` erik quanstrom
2009-03-05 3:32 ` J.R. Mauro
2009-03-05 3:39 ` erik quanstrom
2009-03-05 3:55 ` William K. Josephson
2009-03-05 4:00 ` erik quanstrom
2009-03-05 4:16 ` William K. Josephson
2009-03-07 3:01 ` William Josephson
2009-03-07 3:31 ` erik quanstrom
2009-03-07 6:00 ` William Josephson
2009-03-07 13:58 ` erik quanstrom
2009-03-07 14:37 ` William Josephson [this message]
2009-03-07 15:05 ` erik quanstrom
2009-03-07 15:28 ` William K. Josephson
2009-03-07 5:00 ` lucio
2009-03-07 5:08 ` William Josephson
2009-03-07 5:19 ` erik quanstrom
2009-03-07 5:45 ` [9fans] Flash William K. Josephson
2009-03-07 14:42 ` erik quanstrom
2009-03-07 14:56 ` William Josephson
2009-03-07 15:39 ` Russ Cox
2009-03-07 16:34 ` erik quanstrom
2009-03-07 5:24 ` [9fans] threads vs forks lucio
2009-03-04 5:19 ` David Leimbach
2009-03-04 2:47 ` John Barham
2009-03-04 5:24 ` blstuart
2009-03-04 5:37 ` erik quanstrom
2009-03-04 16:29 ` Roman V Shaposhnik
2009-03-04 16:56 ` john
2009-03-06 9:39 ` maht
2009-03-04 5:07 ` David Leimbach
2009-03-04 5:35 ` John Barham
2009-03-03 16:00 ` ron minnich
2009-03-03 16:28 ` hugo rivera
2009-03-03 17:31 ` ron minnich
2009-03-03 16:47 ` John Barham
2009-03-04 9:37 ` Vincent Schut
2009-03-04 9:58 ` hugo rivera
2009-03-04 10:30 ` Vincent Schut
2009-03-04 10:45 ` hugo rivera
2009-03-04 11:15 ` Vincent Schut
2009-03-04 11:33 ` hugo rivera
2009-03-04 13:23 ` Uriel
2009-03-04 14:57 ` ron minnich
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=20090307143755.GB68357@mero.morphisms.net \
--to=jkw@eecs.harvard.edu \
--cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).