All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@cfl.rr.com>
To: heinzm@redhat.com, device-mapper development <dm-devel@redhat.com>
Subject: Re: Announcement: new device-mapper thin provisioning target with infrastructure online for review
Date: Tue, 25 Jan 2011 15:07:00 -0500	[thread overview]
Message-ID: <4D3F2D64.6060102@cfl.rr.com> (raw)
In-Reply-To: <1295972365.2936.77.camel@o>

On 1/25/2011 11:19 AM, Heinz Mauelshagen wrote:
> Using the thin provisioning target
> 
> Table line syntax (also see thinp_ctr() in dm-thin-prov.c):
> 
> <start> <len> thin-prov \
> <data_dev> <meta_dev> <data_block_size> <low_water_mark>
> 
> * data_dev: device holding thin provisioned data blocks
> * meta_dev: device keeping track of provisioned blocks
> * data_block_size: provisioning unit size in sectors
> * low_water_mark: block low water mark to throw a dm event
>   for userpace to resize

I assume that meta_dev can't, but can data_dev be shared between
multiple thin-prov targets?

  reply	other threads:[~2011-01-25 20:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-25 16:19 Announcement: new device-mapper thin provisioning target with infrastructure online for review Heinz Mauelshagen
2011-01-25 20:07 ` Phillip Susi [this message]
2011-01-26  8:29   ` Joe Thornber

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=4D3F2D64.6060102@cfl.rr.com \
    --to=psusi@cfl.rr.com \
    --cc=dm-devel@redhat.com \
    --cc=heinzm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.