From: Randy Dunlap <randy.dunlap@ORACLE.COM>
To: bo yang <bo.yang@lsi.com>
Cc: linux-scsi@vger.kernel.org, James.Bottomley@SteelEye.com,
akpm@osdl.org, linux-kernel@vger.kernel.org, Bo.yang@lsi.com,
Sumant.patro@lsi.com
Subject: Re: [PATCH 4/8] scsi: megaraid_sas - check max_sgl reported by FW for setting max_sectors_per_req
Date: Fri, 28 Sep 2007 13:44:34 -0700 [thread overview]
Message-ID: <20070928134434.4675c409.randy.dunlap@oracle.com> (raw)
In-Reply-To: <1190820936.5955.17.camel@dhcp-75-534.se.lsil.com>
On Wed, 26 Sep 2007 11:35:36 -0400 bo yang wrote:
> 1. Setting the max_sectors_per_req based on max SGL supported by the FW. Prior versions calculated
> this value from controller info's max_sectors_1, max_sectors_2. For certain controllers/FW,
> this was resulting in a value greater than max SGL supported by the FW. Now we take the min
> of max sgl from FW and max_sectors calculation.
>
> 2. Increased MFI_POLL_TIMEOUT_SECS to 60 seconds from 10. FW may take a max of 60 seconds to
> respond to the INIT cmd.
>
> Signed-off-by: Bo Yang <bo.yang@lsi.com>
>
> ---
> drivers/scsi/megaraid/megaraid_sas.c | 13 +++++++++----
> drivers/scsi/megaraid/megaraid_sas.h | 2 +-
> 2 files changed, 10 insertions(+), 5 deletions(-)
>
> diff -uprN linux-2.6.22_orig/drivers/scsi/megaraid/megaraid_sas.c linux-2.6.22_new/drivers/scsi/megaraid/megaraid_sas.c
> --- linux-2.6.22_orig/drivers/scsi/megaraid/megaraid_sas.c 2007-09-27 20:40:14.000000000 -0700
> +++ linux-2.6.22_new/drivers/scsi/megaraid/megaraid_sas.c 2007-09-27 04:39:44.000000000 -0700
> @@ -1960,6 +1960,7 @@ static int megasas_init_mfi(struct megas
> u32 reply_q_sz;
> u32 max_sectors_1;
> u32 max_sectors_2;
> + u32 tmp_sectors;
> struct megasas_register_set __iomem *reg_set;
> struct megasas_ctrl_info *ctrl_info;
> /*
> @@ -2052,17 +2053,21 @@ static int megasas_init_mfi(struct megas
> * Note that older firmwares ( < FW ver 30) didn't report information
> * to calculate max_sectors_1. So the number ended up as zero always.
> */
> + tmp_sectors = 0;
> if (ctrl_info && !megasas_get_ctrl_info(instance, ctrl_info)) {
>
> max_sectors_1 = (1 << ctrl_info->stripe_sz_ops.min) *
> ctrl_info->max_strips_per_io;
> max_sectors_2 = ctrl_info->max_request_size;
>
> - instance->max_sectors_per_req = (max_sectors_1 < max_sectors_2)
> + tmp_sectors = (max_sectors_1 < max_sectors_2)
> ? max_sectors_1 : max_sectors_2;
tmp_sectors = min_t(u32, max_sectors_1, max_sectors_2);
> - } else
> - instance->max_sectors_per_req = instance->max_num_sge *
> - PAGE_SIZE / 512;
> + }
> +
> + instance->max_sectors_per_req = instance->max_num_sge *
> + PAGE_SIZE / 512;
> + if (tmp_sectors && (instance->max_sectors_per_req > tmp_sectors))
> + instance->max_sectors_per_req = tmp_sectors;
>
> kfree(ctrl_info);
---
~Randy
Phaedrus says that Quality is about caring.
next prev parent reply other threads:[~2007-09-28 20:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 15:35 [PATCH 4/8] scsi: megaraid_sas - check max_sgl reported by FW for setting max_sectors_per_req bo yang
2007-09-28 20:44 ` Randy Dunlap [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-01 15:56 bo yang
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=20070928134434.4675c409.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=James.Bottomley@SteelEye.com \
--cc=Sumant.patro@lsi.com \
--cc=akpm@osdl.org \
--cc=bo.yang@lsi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.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