Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752195AbXLEBMF (ORCPT ); Tue, 4 Dec 2007 20:12:05 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750993AbXLEBLy (ORCPT ); Tue, 4 Dec 2007 20:11:54 -0500 Received: from idcmail-mo1so.shaw.ca ([24.71.223.10]:23766 "EHLO pd2mo1so.prod.shaw.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750764AbXLEBLy (ORCPT ); Tue, 4 Dec 2007 20:11:54 -0500 Date: Tue, 04 Dec 2007 19:11:37 -0600 From: Robert Hancock Subject: Re: solid state drive access and context switching In-reply-to: To: Chris Friesen Cc: linux-kernel@vger.kernel.org Message-id: <4755FAC9.5050901@shaw.ca> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit References: User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1048 Lines: 26 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/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/