From: Robert Hancock <hancockr@shaw.ca>
To: Chris Friesen <cfriesen@nortel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: solid state drive access and context switching
Date: Tue, 04 Dec 2007 19:11:37 -0600 [thread overview]
Message-ID: <4755FAC9.5050901@shaw.ca> (raw)
In-Reply-To: <fa.4uUCLsuQFjc4FtQYCBYK6kY9TiU@ifi.uio.no>
Chris Friesen wrote:
>
> Over on comp.os.linux.development.system someone asked an interesting
> question, and I thought I'd mention it here.
>
> Given a fast low-latency solid state drive, would it ever be beneficial
> to simply wait in the kernel for synchronous read/write calls to
> complete? The idea is that you could avoid at least two task context
> switches, and if the data access can be completed at less cost than
> those context switches it could be an overall win.
>
> Has anyone played with this concept?
I don't think most SSDs are fast enough that it would really be worth
avoiding the context switch for.. I could be wrong though.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2007-12-05 1:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.4uUCLsuQFjc4FtQYCBYK6kY9TiU@ifi.uio.no>
2007-12-05 1:11 ` Robert Hancock [this message]
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
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
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=4755FAC9.5050901@shaw.ca \
--to=hancockr@shaw.ca \
--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