Date: Thu, 26 Jun 2008 10:18:30 -0400 (EDT)
From: Alan Stern <stern@rowland.harvard.edu>
To: Jens Axboe <jens.axboe@oracle.com>
cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>, <andi@firstfloor.org>,
       <linux-kernel@vger.kernel.org>, <antonio.lin@alcormicro.com>,
       <david.vrabel@csr.com>
Subject: Re: Scatter-gather list constraints
In-Reply-To: <20080626063559.GJ20851@kernel.dk>
Message-ID: <Pine.LNX.4.44L0.0806261016590.2811-100000@iolanthe.rowland.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1024
Lines: 22

On Thu, 26 Jun 2008, Jens Axboe wrote:

> I don't think adding anything in the general IO path makes a lot of
> sense, this is a really screwy case. I don't mind adding work-arounds to
> the block layer to cater for hardware weirdness, but this is getting a
> little silly. We could provide a helper function for 'bouncing' this
> request and thus reuse the block bounce buffer for this, but I'm not
> even sure how to simply express this generically. As it is likely of no
> use outside of this specific case, putting it in the driver (or usb
> layer, if you expect more of these similar cases) is the best option.

That sounds great.  If any of you could provide the bounce-buffer 
helper functions, I will be pleased to write the USB-specific code to 
call them.

Alan Stern

--
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/