public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: FUJITA Tomonori <tomof@acm.org>
Cc: James.Bottomley@SteelEye.com, hch@infradead.org, jeff@garzik.org,
	gregkh@suse.de, hare@suse.de, linux-scsi@vger.kernel.org,
	fujita.tomonori@lab.ntt.co.jp
Subject: Re: [PATCH 1/5] add dma_max_segment_size option to scsi_host_template
Date: Wed, 26 Sep 2007 11:05:34 +0200	[thread overview]
Message-ID: <20070926090534.GA4243@kernel.dk> (raw)
In-Reply-To: <20070925142144Z.tomof@acm.org>

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@lab.ntt.co.jp>
> ---
>  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


  reply	other threads:[~2007-09-26  9:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-26  8:57 [PATCH 1/5] add dma_max_segment_size option to scsi_host_template FUJITA Tomonori
2007-09-26  9:05 ` Jens Axboe [this message]
2007-09-26 10:11 ` Jeff Garzik
2007-09-26 14:34   ` FUJITA Tomonori
2007-09-26 14:42     ` Jeff Garzik
2007-09-27  0:37       ` FUJITA Tomonori
2007-09-27  6:31         ` Jeff Garzik
2007-09-29  6:30           ` FUJITA Tomonori

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070926090534.GA4243@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=gregkh@suse.de \
    --cc=hare@suse.de \
    --cc=hch@infradead.org \
    --cc=jeff@garzik.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=tomof@acm.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox