From: Jens Axboe Subject: Re: [PATCH] BLOCK: Make it possible to disable the block layer Date: Fri, 25 Aug 2006 14:16:21 +0200 Message-ID: <20060825121621.GA24258@kernel.dk> References: <32640.1156424442@warthog.cambridge.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Return-path: Received: from brick.kernel.dk ([62.242.22.158]:572 "EHLO kernel.dk") by vger.kernel.org with ESMTP id S1751171AbWHYMNz (ORCPT ); Fri, 25 Aug 2006 08:13:55 -0400 To: David Howells Content-Disposition: inline In-Reply-To: <32640.1156424442@warthog.cambridge.redhat.com> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Thu, Aug 24 2006, David Howells wrote: > > Make it possible to disable the block layer. Not all embedded devices require > it, some can make do with just JFFS2, NFS, ramfs, etc - none of which require > the block layer to be present. Overall, this looks good. It's definitely something that has been talked about for years (off and on), but nobody ever did. So thanks David! When you respin this patch, care to do it against the 'block' branch of the git block repo? > (*) The SCSI layer. As far as I can tell, even SCSI chardevs use the > block layer to do scheduling. SCSI uses the queue as the transport even for char devices, so yes you have to leave all of SCSI behind. -- Jens Axboe