From: Andrew Morton <akpm@linux-foundation.org>
To: "Stephen M. Cameron" <scameron@beardog.cce.hp.com>
Cc: axboe@kernel.dk, stephenmcameron@gmail.com,
mikem@beardog.cce.hp.com, linux-kernel@vger.kernel.org,
thenzl@redhat.com
Subject: Re: [PATCH] cciss: Initialize scsi host max_sectors for tape drive support
Date: Wed, 21 Mar 2012 14:44:31 -0700 [thread overview]
Message-ID: <20120321144431.044d3af3.akpm@linux-foundation.org> (raw)
In-Reply-To: <20120321213203.9277.11716.stgit@beardog.cce.hp.com>
On Wed, 21 Mar 2012 16:32:03 -0500
"Stephen M. Cameron" <scameron@beardog.cce.hp.com> wrote:
> From: Stephen M. Cameron <scameron@beardog.cce.hp.com>
>
> The default is too small
So is the changelog.
> (1024 blocks), use h->cciss_max_sectors (8192 blocks)
What problem does this patch solve? What might be the user-visible
effects of the change?
> Signed-off-by: Stephen M. Cameron <scameron@beardog.cce.hp.com>
> ---
> drivers/block/cciss_scsi.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/block/cciss_scsi.c b/drivers/block/cciss_scsi.c
> index e820b68..f510a9c 100644
> --- a/drivers/block/cciss_scsi.c
> +++ b/drivers/block/cciss_scsi.c
> @@ -866,6 +866,7 @@ cciss_scsi_detect(ctlr_info_t *h)
> sh->can_queue = cciss_tape_cmds;
> sh->sg_tablesize = h->maxsgentries;
> sh->max_cmd_len = MAX_COMMAND_SIZE;
> + sh->max_sectors = h->cciss_max_sectors;
>
> ((struct cciss_scsi_adapter_data_t *)
> h->scsi_ctlr)->scsi_host = sh;
prev parent reply other threads:[~2012-03-21 21:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 21:32 [PATCH] cciss: Initialize scsi host max_sectors for tape drive support Stephen M. Cameron
2012-03-21 21:44 ` Andrew Morton [this message]
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=20120321144431.044d3af3.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=mikem@beardog.cce.hp.com \
--cc=scameron@beardog.cce.hp.com \
--cc=stephenmcameron@gmail.com \
--cc=thenzl@redhat.com \
/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