From: "Jörn Engel" <joern@logfs.org>
To: Jared Hulbert <jaredeh@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Chris Friesen <cfriesen@nortel.com>,
linux-kernel@vger.kernel.org
Subject: Re: solid state drive access and context switching
Date: Tue, 4 Dec 2007 23:45:25 +0100 [thread overview]
Message-ID: <20071204224525.GC26112@lazybastard.org> (raw)
In-Reply-To: <6934efce0712041354n47c11d6ckbc7f4aa1e7c85f@mail.gmail.com>
On Tue, 4 December 2007 13:54:21 -0800, Jared Hulbert wrote:
>
> Maybe I'm missing something but I don't see it. We want a block
> interface for these devices, we just need a faster slimmer interface.
> Maybe a new mtdblock interface that doesn't do erase would be the
> place for?
Doesn't do erase? MTD has to learn almost all tricks from the block
layer, as devices are becoming high-latency high-bandwidth, compared to
what MTD was designed for. In order to get any decent performance, we
need asynchronous operations, request queues and caching.
The only useful advantage MTD does have over block devices is an
_explicit_ erase operation. Did you mean "doesn't do _implicit_ erase".
Jörn
--
It's just what we asked for, but not what we want!
-- anonymous
next prev parent reply other threads:[~2007-12-04 22:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-03 23:06 solid state drive access and context switching 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 [this message]
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
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=20071204224525.GC26112@lazybastard.org \
--to=joern@logfs.org \
--cc=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