[dm-devel] device mapper target vs personality, how do you decide to pick one or the other?
John.Utz at wdc.com
Fri Jul 11 21:56:44 UTC 2014
tnx so much for the prompt response!
sorry i wasnt clear enuf, example of the 'personality code' that i was writing about below.
(and apologies in advance for my outlook web access MUA's lack of appropriate citing technology)
From: Mike Snitzer [snitzer at redhat.com]
Sent: Friday, July 11, 2014 2:51 PM
To: John Utz
Cc: dm-devel at redhat.com
Subject: Re: device mapper target vs personality, how do you decide to pick one or the other?
On Fri, Jul 11 2014 at 5:28pm -0400,
John Utz <John.Utz at wdc.com> wrote:
> having stared at the code associated with these 2 constructs for a while, i cant come up with a clear reason why one would choose one over the other.
> having said that, it seems that the personality code is ancestral and
> is used for the personalities that can be compiled into device mapper
> and the target code is for newer stuff that is not expected to be
> compiled into device mapper.
Not sure I know what you mean by "personality code" in DM.
FOR EXAMPLE, here is a little bit of linear.c that contains it:
static struct md_personality linear_personality =
.name = "linear",
.level = LEVEL_LINEAR,
.owner = THIS_MODULE,
.make_request = linear_make_request,
.run = linear_run,
.stop = linear_stop,
.status = linear_status,
.hot_add_disk = linear_add,
.size = linear_size,
static int __init linear_init (void)
return register_md_personality (&linear_personality);
static void linear_exit (void)
> so, based on this speculation, i *think* i should be using the target
> construct for the new device mapper module that i am currently
> am i correct?
More information about the dm-devel