All of lore.kernel.org
 help / color / mirror / Atom feed
From: Asai Thambi S P <asamymuthupa@micron.com>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Sam Bradshaw <sbradshaw@micron.com>
Subject: Re: [PATCH 05/11] mtip32xx: Set block queue boundary variables
Date: Thu, 31 May 2012 11:12:33 -0700	[thread overview]
Message-ID: <4FC7B491.9030105@micron.com> (raw)
In-Reply-To: <x49sjegb7h4.fsf@segfault.boston.devel.redhat.com>

On 5/31/2012 10:12 AM, Jeff Moyer wrote:

> Asai Thambi S P <asamymuthupa@micron.com> writes:
> 
>> On 5/30/2012 11:43 PM, Jens Axboe wrote:
>>
>>> On 05/30/2012 03:42 AM, Asai Thambi S P wrote:
>>>>
>>>> Set the following block queue boundary variables
>>>> 	* max_hw_sectors
>>>> 	* max_segment_size
>>>> 	* nr_requests
>>>>
>>>> Signed-off-by: Asai Thambi S P <asamymuthupa@micron.com>
>>>> ---
>>>>  drivers/block/mtip32xx/mtip32xx.c |    4 ++++
>>>>  1 files changed, 4 insertions(+), 0 deletions(-)
>>>>
>>>> diff --git a/drivers/block/mtip32xx/mtip32xx.c b/drivers/block/mtip32xx/mtip32xx.c
>>>> index 9fe897d..801e70c 100644
>>>> --- a/drivers/block/mtip32xx/mtip32xx.c
>>>> +++ b/drivers/block/mtip32xx/mtip32xx.c
>>>> @@ -3631,7 +3631,11 @@ skip_create_disk:
>>>>  	set_bit(QUEUE_FLAG_NONROT, &dd->queue->queue_flags);
>>>>  	blk_queue_max_segments(dd->queue, MTIP_MAX_SG);
>>>>  	blk_queue_physical_block_size(dd->queue, 4096);
>>>> +	blk_queue_max_hw_sectors(dd->queue, 0xffff);
>>>> +	blk_queue_max_segment_size(dd->queue, 0x400000);
>>>>  	blk_queue_io_min(dd->queue, 4096);
>>>> +	dd->queue->nr_requests = 255;
>>>
>>> ->nr_requests isn't a boundary variable you set for the queue. It's set
>>> by the core bits, or by the user via the sysfs interface.
>>>
>>> So you should not touch that from the driver.
>>>
>>
>> Ok.
>>
>> I saw scsi lib module changing it, so thought of changing the value close to
>> device queue depth.
> 
> That's actually a fair point.  What is the device queue depth for this
> card?
> 


256

  reply	other threads:[~2012-05-31 18:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-30  1:42 [PATCH 05/11] mtip32xx: Set block queue boundary variables Asai Thambi S P
2012-05-31  6:43 ` Jens Axboe
2012-05-31 15:56   ` Asai Thambi S P
2012-05-31 17:12     ` Jeff Moyer
2012-05-31 18:12       ` Asai Thambi S P [this message]
2012-05-31 18:40         ` Jeff Moyer
2012-06-01  6:01           ` Jens Axboe
2012-06-01 13:11             ` Jeff Moyer

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=4FC7B491.9030105@micron.com \
    --to=asamymuthupa@micron.com \
    --cc=axboe@kernel.dk \
    --cc=jmoyer@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sbradshaw@micron.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.