Messages in this thread |  | | | Date | Tue, 23 Jan 2007 15:15:01 +0200 | | From | Benny Halevy <> | | Subject | Re: [RFC 3/6] bidi support: bidirectional request |
| |
James Bottomley wrote: > On Mon, 2007-01-22 at 01:25 +0200, Boaz Harrosh wrote: >> - Instantiate another request_io_part in request for bidi_read. >> - Define & Implement new API for accessing bidi parts. >> - API to Build bidi requests and map to sglists. >> - Define new end_that_request_block() function to end a complete request. > > Actually, this approach looks to be a bit too narrow. You seem to be > predicating on the idea that the bidirectional will transfer in and out > of the same area. For some of the frame in/frame out stuff, we probably > need the read and write areas for the bidirectional request to be > separated.
Hmm, our proposal introduces two separate and independent i/o areas. One used for uni-directional transfers and for bidi data output, the other is used for bidi data input so we're in agreement.
Benny
- 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/
|  |