Linux Device Mapper development
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: device-mapper development <dm-devel@redhat.com>
Cc: Alasdair Kergon <agk@redhat.com>
Subject: Re: [PATCH 3/7] dm core: enable request-based dm
Date: Fri, 24 Apr 2009 10:50:50 +0200	[thread overview]
Message-ID: <49F17D6A.3020305@suse.de> (raw)
In-Reply-To: <49F174CD.403@ct.jp.nec.com>

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
> 
>   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 binding time.
>   Once the type of a dm device is decided, the type can't be changed.
> 
> o Mempool allocations are deferred to at the table loading time, since
>   mempools for request-based dm are different from those for bio-based
>   dm and needed mempool type is fixed by the type of table.
> 
> o Currently, request-based dm supports only tables that have a single
>   target.  To support multiple targets, we need to support request
>   splitting or prevent bio/request from spanning multiple targets.
>   The former needs lots of changes in the block layer, and the latter
>   needs that all target drivers support merge() function.
>   Both will take a time.
> 
> 
> Signed-off-by: Kiyoshi Ueda <k-ueda@ct.jp.nec.com>
> Signed-off-by: Jun'ichi Nomura <j-nomura@ce.jp.nec.com>
Acked-by: Hannes Reinecke <hare@suse.de>

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)

  reply	other threads:[~2009-04-24  8:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-24  8:10 [PATCH 0/7] request-based dm-multipath (v2) Kiyoshi Ueda
2009-04-24  8:12 ` [PATCH 1/7] dm core: add core functions for request-based dm Kiyoshi Ueda
2009-04-24  8:45   ` Hannes Reinecke
2009-04-24  8:13 ` [PATCH 2/7] dm core: add integrity feature to " Kiyoshi Ueda
2009-04-24  8:46   ` Hannes Reinecke
2009-04-24  8:14 ` [PATCH 3/7] dm core: enable " Kiyoshi Ueda
2009-04-24  8:50   ` Hannes Reinecke [this message]
2009-04-24  8:14 ` [PATCH 4/7] dm core: don't set QUEUE_ORDERED_DRAIN for " Kiyoshi Ueda
2009-04-24  8:51   ` Hannes Reinecke
2009-04-24  8:15 ` [PATCH 5/7] dm core: reject I/O violating new queue limits Kiyoshi Ueda
2009-04-24  8:59   ` Hannes Reinecke
2009-04-28  7:49     ` Kiyoshi Ueda
2009-06-23  5:46       ` Kiyoshi Ueda
2009-04-24  8:15 ` [PATCH 6/7] dm core: disable interrupt when taking map_lock Kiyoshi Ueda
2009-04-24  9:00   ` Hannes Reinecke
2009-04-24 11:50   ` Christof Schmitt
2009-04-24  8:16 ` [PATCH 7/7] dm-mpath: convert to request-based Kiyoshi Ueda
2009-04-24  9:04   ` Hannes Reinecke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49F17D6A.3020305@suse.de \
    --to=hare@suse.de \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox