[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20081028.120351.78702656.k-ueda@ct.jp.nec.com>
Date: Tue, 28 Oct 2008 12:03:51 -0400 (EDT)
From: Kiyoshi Ueda <k-ueda@...jp.nec.com>
To: nikanth@...il.com
Cc: dm-devel@...hat.com, jens.axboe@...cle.com, agk@...hat.com,
James.Bottomley@...senpartnership.com, j-nomura@...jp.nec.com,
linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org,
knikanth@...e.de, k-ueda@...jp.nec.com
Subject: Re: [dm-devel] [PATCH 13/13] dm-mpath: convert to request-based
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists