From: "Jared Hulbert" <jaredeh@gmail.com>
To: "Chris Friesen" <cfriesen@nortel.com>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: solid state drive access and context switching
Date: Tue, 4 Dec 2007 13:38:59 -0800 [thread overview]
Message-ID: <6934efce0712041338g75bec69co1cba9ce0cc9255b9@mail.gmail.com> (raw)
In-Reply-To: <4755BC97.7050607@nortel.com>
> > refinements could theoretically get us down one more (~100
> > microsecond).
>
> They've already done already better than that. Here's a solid state
> drive with a claimed 20 microsecond access time:
>
> http://www.curtisssd.com/products/drives/hyperxclr
Right. That looks to be RAM based, which means $$$$ compared to NAND,
so that's not going to breakout of a server niche. I imagine the
latency is the device latency not the system latency. By the time you
send the request through the fibrechannel stack and get the block back
it's gonna be much closer to 100 microseconds. It's that OS visible
latency that you've got to design to.
next prev parent reply other threads:[~2007-12-04 21:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-03 23:06 Chris Friesen
2007-12-03 23:06 ` Alan Cox
2007-12-04 17:54 ` Jared Hulbert
2007-12-04 20:35 ` Alan Cox
2007-12-04 21:54 ` Jared Hulbert
2007-12-04 22:45 ` Jörn Engel
2007-12-05 0:03 ` Jared Hulbert
2007-12-04 23:24 ` Alan Cox
2007-12-05 0:08 ` Jared Hulbert
2007-12-05 0:24 ` Alan Cox
2007-12-05 22:01 ` Jared Hulbert
2007-12-06 3:51 ` Kyungmin Park
2007-12-04 20:46 ` Chris Friesen
2007-12-04 21:38 ` Jared Hulbert [this message]
2007-12-04 20:52 ` Jeff Garzik
2007-12-04 21:02 ` Alan Cox
[not found] <fa.4uUCLsuQFjc4FtQYCBYK6kY9TiU@ifi.uio.no>
2007-12-05 1:11 ` Robert Hancock
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=6934efce0712041338g75bec69co1cba9ce0cc9255b9@mail.gmail.com \
--to=jaredeh@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cfriesen@nortel.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®