On Wed, Sep 26 2007, FUJITA Tomonori wrote: > This patch moves blk_queue_max_segment_size to scsi_alloc_queue from > llds. It enables scsi_add_host to tells iommu lld's > dma_max_segment_size. If a low-level driver doesn't specify > dma_max_segment_size, scsi-ml uses 65536 (MAX_SEGMENT_SIZE). So there > are not any functional changes. > > Signed-off-by: FUJITA Tomonori <fujita.tomonori@xxxxxxxxxxxxx> > --- > drivers/scsi/hosts.c | 5 +++++ > drivers/scsi/scsi_lib.c | 1 + > include/scsi/scsi_host.h | 6 ++++++ > 3 files changed, 12 insertions(+), 0 deletions(-) > > diff --git a/drivers/scsi/hosts.c b/drivers/scsi/hosts.c > index 96bc312..22877d3 100644 > --- a/drivers/scsi/hosts.c > +++ b/drivers/scsi/hosts.c > @@ -365,6 +365,11 @@ struct Scsi_Host *scsi_host_alloc(struct scsi_host_template *sht, int privsize) > else > shost->dma_boundary = 0xffffffff; > > + if (sht->dma_max_segment_size) > + shost->dma_max_segment_size = sht->dma_max_segment_size; > + else > + shost->dma_max_segment_size = 65536; Use MAX_SEGMENT_SIZE here, instead of manually entering 64k? Otherwise everything looks good from a quick look, it's definitely missing functionality that we have wanted for quite some time! -- Jens Axboe - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
