[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20081028.120227.104028516.k-ueda@ct.jp.nec.com>
Date: Tue, 28 Oct 2008 12:02:27 -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 11/13] dm: enable request-based dm
Hi Nikanth,
On Fri, 24 Oct 2008 13:22:46 +0530, "Nikanth K" wrote:
> On Fri, Sep 12, 2008 at 8:16 PM, Kiyoshi Ueda wrote:
> > This patch enables request-based dm.
> >
> > o Request-based dm and bio-based dm coexist, since there are
> > some target drivers which are more fitting to bio-based dm.
> > Also, there are other bio-based devices in the kernel
> > (e.g. md, loop).
> > Since bio-based device can't receive struct request,
> > there are some limitations on device stacking between
> > bio-based and request-based.
> >
> > type of underlying device
> > bio-based requeset-based
> > ----------------------------------------------
> > bio-based OK OK
> > request-based NG OK
> >
>
> So will some configurations would become impossible, if a target is
> made request-based and bio-based one is removed. Hope both
> types of targets would co-exist and would be selectable for sometime.
If the target is used anywhere in the device stack (e.g. linear),
both types of the target are needed, and that is possible.
As for multipath, see my another reply to your comment for PATCH 13.
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