linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: David Howells <dhowells@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] BLOCK: Make it possible to disable the block layer
Date: Fri, 25 Aug 2006 14:16:21 +0200	[thread overview]
Message-ID: <20060825121621.GA24258@kernel.dk> (raw)
In-Reply-To: <32640.1156424442@warthog.cambridge.redhat.com>

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


  parent reply	other threads:[~2006-08-25 12:13 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-24 13:00 [PATCH] BLOCK: Make it possible to disable the block layer David Howells
2006-08-24 13:13 ` David Woodhouse
2006-08-24 13:34 ` David Howells
2006-08-24 13:40   ` David Woodhouse
2006-08-24 13:54   ` David Howells
2006-08-24 13:47 ` Christoph Hellwig
2006-08-24 14:42 ` Nick Piggin
2006-08-24 15:29 ` Adrian Bunk
2006-08-24 15:44   ` David Woodhouse
2006-08-24 15:58     ` Adrian Bunk
2006-08-24 16:00       ` David Woodhouse
2006-08-24 16:09         ` Adrian Bunk
2006-08-24 16:47           ` Alexey Dobriyan
2006-08-24 17:07             ` Adrian Bunk
2006-08-24 17:16               ` David Woodhouse
2006-08-24 17:34                 ` Randy.Dunlap
2006-08-24 17:48                   ` David Woodhouse
2006-08-24 17:59                     ` Sam Ravnborg
2006-08-25  6:23                       ` Jan Engelhardt
2006-08-25  7:19                         ` Sam Ravnborg
2006-08-24 18:01                     ` Randy.Dunlap
2006-08-25  6:21                 ` Jan Engelhardt
2006-08-25  6:07               ` Jan Engelhardt
2006-08-25 10:37                 ` Adrian Bunk
2006-08-25 13:09                   ` Alexey Dobriyan
2006-08-24 16:39       ` Jan Engelhardt
2006-08-24 16:44         ` David Woodhouse
2006-08-24 16:48         ` Adrian Bunk
2006-08-24 21:31           ` Johannes Stezenbach
2006-08-25  6:04           ` Jan Engelhardt
2006-08-24 18:39         ` Matthias Schniedermeyer
2006-08-25  6:06           ` Jan Engelhardt
2006-08-24 17:18     ` David Howells
2006-08-24 17:23       ` Adrian Bunk
2006-08-24 16:23 ` Stefan Richter
2006-08-25 12:16 ` Jens Axboe [this message]
2006-08-25 13:40 ` David Howells

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=20060825121621.GA24258@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=dhowells@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).