Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752217AbXLCXGm (ORCPT ); Mon, 3 Dec 2007 18:06:42 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750964AbXLCXGf (ORCPT ); Mon, 3 Dec 2007 18:06:35 -0500 Received: from zrtps0kp.nortel.com ([47.140.192.56]:42486 "EHLO zrtps0kp.nortel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750979AbXLCXGe (ORCPT ); Mon, 3 Dec 2007 18:06:34 -0500 Message-ID: <47548BF4.3010907@nortel.com> Date: Mon, 03 Dec 2007 17:06:28 -0600 From: "Chris Friesen" User-Agent: Mozilla Thunderbird 1.0.2-6 (X11/20050513) X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-kernel@vger.kernel.org Subject: solid state drive access and context switching Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 03 Dec 2007 23:06:31.0306 (UTC) FILETIME=[245DE6A0:01C83601] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 740 Lines: 20 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? Chris -- 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/