Date: Tue, 9 Nov 2004 11:53:38 -0800
From: Andrew Morton <akpm@osdl.org>
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org, Neil Brown <neilb@cse.unsw.edu.au>
Subject: Re: 2.6.10-rc1-mm4
Message-Id: <20041109115338.59d195ec.akpm@osdl.org>
In-Reply-To: <20041109161112.GA3921@suse.de>
References: <20041109074909.3f287966.akpm@osdl.org>
	<20041109161112.GA3921@suse.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 915
Lines: 21

Jens Axboe <axboe@suse.de> wrote:
>
> On Tue, Nov 09 2004, Andrew Morton wrote:
> > +blk_sync_queue-updates.patch
> > 
> >  update an update to the md updates
> 
> I still don't think this is a good general export, it has very
> specialized use. For example, from the description it looks like this
> can be generally used on any block device and when it returns, we have
> synced the queue. This simply isn't true, there are absolutely no
> guarentees of that nature unless the block driver itself implements the
> __make_request() functionality and has taken proper precautions to
> prevent this already.

True.   So what do we do?  Grit our teeth and move it into MD?
-
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/