[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [dm-devel] [PATCH 0/2] dm: Add no_abort_q feature flag to dm-mpath
- From: "Moger, Babu" <Babu Moger lsi com>
- To: Mike Anderson <andmike linux vnet ibm com>, "dm-devel redhat com" <dm-devel redhat com>
- Cc: "linux-scsi vger kernel org" <linux-scsi vger kernel org>
- Subject: Re: [dm-devel] [PATCH 0/2] dm: Add no_abort_q feature flag to dm-mpath
- Date: Wed, 5 May 2010 17:19:57 -0600
> -----Original Message-----
> From: linux-scsi-owner vger kernel org [mailto:linux-scsi-
> owner vger kernel org] On Behalf Of Mike Anderson
> Sent: Monday, May 03, 2010 11:01 PM
> To: dm-devel redhat com
> Cc: linux-scsi vger kernel org
> Subject: [PATCH 0/2] dm: Add no_abort_q feature flag to dm-mpath
>
> This patch series contains two patches.
>
> 1.) The first patch adds a feature flags bit field to the multipath
> structure for selected features.
>
> 2.) The second patch allows a user to set a feature flag for a dm-mpath
> device of "no_abort_q" to indicate that deactivate_path should not call
> blk_abort_queue. I tried to select a short feature name to feature
> output
> listed with multipath -l would not be too long "features='2
> queue_if_no_path
> no_abort_q'
Mike,
In what special circumstances you recommend to use this feature? It would be great if you could add that explanation in your patch descriptions.
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]