[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [dm-devel] [PATCH v2] block: do not artificially constrain max_sectors for stacking drivers
- From: "Chauhan, Vijay" <Vijay Chauhan netapp com>
- To: Mike Snitzer <snitzer redhat com>
- Cc: "axboe kernel dk" <axboe kernel dk>, "Martin K. Petersen" <martin petersen oracle com>, "dm-devel redhat com" <dm-devel redhat com>, "linux-kernel vger kernel org" <linux-kernel vger kernel org>, "Moger, Babu" <Babu Moger netapp com>, "Stankey, Robert" <Robert Stankey netapp com>
- Subject: Re: [dm-devel] [PATCH v2] block: do not artificially constrain max_sectors for stacking drivers
- Date: Tue, 10 Jul 2012 19:10:51 +0000
On Tuesday, July 10, 2012 4:27 AM, Mike Wrote:
>As it happens, v2's changes to blk_limits_max_hw_sectors and
>blk_queue_max_hw_sectors are not strictly required in order for existing
>stacking drivers to have have an unconstrained max_sectors. Dropping
>those changes also allows for consistency across both block functions.
>
>So I'd be happy if v1 were to be staged for 3.6. NetApp: it would be
>great if you could confirm that v1 does in fact address the max_sectors
>issue you reported.
>
>Thanks,
>Mike
Mike, Thanks for the quick fix. I verified with Patch v1 and it resolves this issue.
Thanks,
Vijay
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]