All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fb.com>
To: device-mapper development <dm-devel@redhat.com>,
	Mike Snitzer <snitzer@redhat.com>
Subject: Re: Question about dm target size
Date: Wed, 12 Nov 2014 06:00:00 -0500	[thread overview]
Message-ID: <54633DB0.8050800@fb.com> (raw)
In-Reply-To: <54631E1B.4090300@redhat.com>

On 11/12/2014 03:45 AM, Zdenek Kabelac wrote:
> Dne 12.11.2014 v 03:30 Josef Bacik napsal(a):
>> Sorry for top posting, my phone client doesn't do inline.
>>
>> I'm splitting the disk in half, writing to alternating sides of the
>> disk and keeping track of where which block is so when the power fail
>> event occurs the subsequent reads come from the corresponding mirror
>> in the disk. The disk needs to appear to be size/2 for the mkfs to
>> know the correct size, but my target needs to be able to write up to
>> size.  I looked at thinp but it reflects the full size right? It's
>> just like a sparse find correct? My ->map function does the right
>> thing, doing the ->len trick makes it all work out right, but this is
>> really isolated testing. Thanks,
>>
>
> Just a side note - maybe you would like to rather extend functionality
> of dm-flakey  target ?
>

I did that first but it ended up being really ugly.  With all the 
varying functionality in dm-flakey it ended up making the table format 
horrible and the code a spaghetti of if (test_bit()) crap everywhere. 
Thanks,

Josef

  reply	other threads:[~2014-11-12 11:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-12  0:37 Question about dm target size Josef Bacik
2014-11-12  2:06 ` Mike Snitzer
2014-11-12  2:30   ` Josef Bacik
2014-11-12  8:45     ` Zdenek Kabelac
2014-11-12 11:00       ` Josef Bacik [this message]
2014-11-12 11:48         ` Zdenek Kabelac
2014-11-12 11:15 ` Heinz Mauelshagen
2014-11-12 12:28 ` Bryn M. Reeves

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=54633DB0.8050800@fb.com \
    --to=jbacik@fb.com \
    --cc=dm-devel@redhat.com \
    --cc=snitzer@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.