James Bottomley wrote: > On Mon, 2008-02-04 at 00:14 +0900, Tejun Heo wrote: >> James Bottomley wrote: >>> I'm reluctant to add another parameter to the request, but this one you >>> can calculate: you just do it wherever you work out the size of the >>> request. If data_len is the true data length and total_data_len is the >>> data length plus the drain length, the calculation fragment is >>> >>> if (blk_pc_request(req)) >>> data_len = req->data_len; >>> else >>> data_len = req->nr_sectors << 9; >>> total_data_len = data_len + req->q->dma_drain_size; >>> >>> If the request has already been mapped by scsi, then data_len is >>> actually scsi_cmnd->sdb.length >> We either need to add a field or a helper and rq->data_len should >> probably record the size with drain buffer attached and either add >> raw_data_len or blk_rq_raw_data_len(). That size is the length of data >> in sg and should be programmed into the controller etc... For ATAPI the >> raw size is only used to program the chunk size for odd devices. > > OK, could you show me an example of where you need it and I'll come up > with the macro ... that should also help us decide whether it needs to > be in block or in libata alone. Note that aic94xx only wants the true > size (we effectively treat the drain element as non existent), and I > anticipate this being true of most conforming implementations. It's > only the problem HBAs that need to know how much slack they have for DMA > overruns. Some ATA controllers including SFF BMDMA and libata PIO HSM need the number of bytes mapped in the sg table. Yeah, it can be calculated with a simple macro but it also is a fundamentally confusing dual-sizing which should be made as clear as possible. Plus, it can be difficult to find out when somebody used the wrong thing, so what I'm saying is that we need to make it easy. Anyways, please lemme work on it a bit. I'll get back to you guys soon. Thanks. -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
