From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Jared Hulbert" <jaredeh@gmail.com>
Cc: "Chris Friesen" <cfriesen@nortel.com>, linux-kernel@vger.kernel.org
Subject: Re: solid state drive access and context switching
Date: Wed, 5 Dec 2007 00:24:54 +0000 [thread overview]
Message-ID: <20071205002454.52ea755c@the-village.bc.nu> (raw)
In-Reply-To: <6934efce0712041608w2e25587n6b2d738fa0265d9d@mail.gmail.com>
On Tue, 4 Dec 2007 16:08:07 -0800
"Jared Hulbert" <jaredeh@gmail.com> wrote:
> On Dec 4, 2007 3:24 PM, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > > Right. The trend is to hide the nastiness of NAND technology changes
> > > behind controllers. In general I think this is a good thing.
> >
> > You miss the point - any controller you hide it behind almost inevitably
> > adds enough latency you don't want to use it synchronously.
>
> I think I get it. We keep saying that it's the latency is too high.
> I agree that most technologies out there have latencies that are too
> high. Again I ask the question, what latencies do we have to hit
> before the sync options become worth it?
Probably about 1000 clocks but its always going to depend upon the
workload and whether any other work can be done usefully.
Alan
next prev parent reply other threads:[~2007-12-05 0:29 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 [this message]
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
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=20071205002454.52ea755c@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=cfriesen@nortel.com \
--cc=jaredeh@gmail.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®