[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [dm-devel] [PATCH 13/13] dm-mpath: convert to request-based
- From: Kiyoshi Ueda <k-ueda ct jp nec com>
- To: nikanth gmail com
- Cc: k-ueda ct jp nec com, linux-scsi vger kernel org, knikanth suse de, linux-kernel vger kernel org, dm-devel redhat com, jens axboe oracle com, j-nomura ce jp nec com, agk redhat com
- Subject: Re: [dm-devel] [PATCH 13/13] dm-mpath: convert to request-based
- Date: Tue, 28 Oct 2008 12:03:51 -0400 (EDT)
Hi Nikanth,
On Fri, 24 Oct 2008 13:25:33 +0530, "Nikanth K" wrote:
> On Fri, Sep 12, 2008 at 8:17 PM, Kiyoshi Ueda wrote:
> > This patch converts dm-multipath target to request-based from bio-based.
>
> Can we keep both the bio-based as well as request-based dm-multipath?
Why do you want to keep bio-based dm-multipath?
In the realistic environment, dm-multipath is usually the bottom
of the stacking devices. So I think existing working configurations
are still possible with request-based dm-multipath.
If we keep both types of multipath targets, maintenance cost would
be doubled and additional user interface might be needed to specify
which type is used. I can't see any major benefit worth paying
the cost of keeping bio-based dm-multipath.
I know dm developers sometimes use linear/error maps under multipath
just for testing purpose. If that is your requirement, I can make
request-based targets for linear and error (e.g. named like linear_rq
and error_rq).
Thanks,
Kiyoshi Ueda
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]