linux-kernel - Re: [dm-devel] [PATCH 11/13] dm: enable request-based dm

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <807b3a220810240052n6a8b41b0x1ea9c88124b3f5f8@mail.gmail.com>
Date:	Fri, 24 Oct 2008 13:22:46 +0530
From:	"Nikanth K" <nikanth@...il.com>
To:	"device-mapper development" <dm-devel@...hat.com>
Cc:	jens.axboe@...cle.com, agk@...hat.com,
	James.Bottomley@...senpartnership.com, j-nomura@...jp.nec.com,
	k-ueda@...jp.nec.com, linux-kernel@...r.kernel.org,
	linux-scsi@...r.kernel.org,
	"Nikanth Karthikesan" <knikanth@...e.de>
Subject: Re: [dm-devel] [PATCH 11/13] dm: enable request-based dm

On Fri, Sep 12, 2008 at 8:16 PM, Kiyoshi Ueda <k-ueda@...jp.nec.com> 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.

>  The device type is recognized by the queue flag in the kernel,
>  so dm follows that.
>
> o The type of a dm device is decided at the first table loading time.
>  Until then, mempool creations are deferred, since mempools for
>  request-based dm are different from those for bio-based dm.
>  Once the type of a dm device is decided, the type can't be changed.
>
> o Currently, request-based dm supports only tables that have a single
>  target.

Barrier support should be straight forward?

Thanks
Nikanth Karthikesan
--
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/