[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [dm-devel] [PATCH] DM MULTIPATH: Allow dm to send larger request if underlying device set to larger max_sectors value
- From: "Chauhan, Vijay" <Vijay Chauhan netapp com>
- To: Alasdair G Kergon <agk redhat com>
- Cc: "dm-devel redhat com" <dm-devel redhat com>, "Moger, Babu" <Babu Moger netapp com>, "Stankey, Robert" <Robert Stankey netapp com>
- Subject: Re: [dm-devel] [PATCH] DM MULTIPATH: Allow dm to send larger request if underlying device set to larger max_sectors value
- Date: Mon, 9 Jul 2012 12:34:08 +0000
Hi Alasdair,
On July 09, 2012 6:32 AM, Alasdair Wrote:
>
>Why is this separate from dm_set_device_limits?
Ideally it should have been taken care in dm_set_device_limits but to find
minimum of max_sectors value among physical paths in dm_set_device_limits seems tricky.
I will look into it to use dm_set_device_limits.
>Why is this not handled by blk-settings.c?
blk_stack_limits do compare max_sectors between dm & physical path and minimum
between two values is then set to max_sectors of dm. But if underlying paths
are set with higher value, dm's max_sectors will be always set to default being
minimum. Rather objective is to set minimum of max_sectors among underlying paths but
not exceeding dm's max_hw_max_sectors
>Should max_sectors be preserved across a table reload?
Intentions is to set max_sectors to maximum capable when dm device is created. Even if
we reset max_sectors_kb from sysfs, restart of multipathd would again reset it to default.
Not sure if I answered your question.
Thanks,
Vijay
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]