All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: John Utz <John.Utz@wdc.com>
Cc: "dm-devel@redhat.com" <dm-devel@redhat.com>
Subject: Re: if i create a new dm target type, do i need to add its init to the _inits[] and its exit to the _exits[]?
Date: Wed, 7 May 2014 09:09:47 -0400	[thread overview]
Message-ID: <20140507130946.GA29851@redhat.com> (raw)
In-Reply-To: <8A51900D08212F40B3DE22453052F6981D0F0297@wdscexmb02>

On Wed, May 07 2014 at 12:45am -0400,
John Utz <John.Utz@wdc.com> wrote:

> Hello;
> 
> While looking thru dm.c trying to figure out how to add new target
> specific errors and sense codes I came across the following arrays:
> 
> static int (*_inits[])(void) __initdata = {
>         local_init,
>         dm_target_init,
>         dm_linear_init,
>         dm_stripe_init,
>         dm_io_init,
>         dm_kcopyd_init,
>         dm_interface_init,
>         dm_statistics_init,
> };
> 
> static void (*_exits[])(void) = {
>         local_exit,
>         dm_target_exit,
>         dm_linear_exit,
>         dm_stripe_exit,
>         dm_io_exit,
>         dm_kcopyd_exit,
>         dm_interface_exit,
>         dm_statistics_exit,
> };
> 
> 
> What are the rules for what goes in to these? I don't see every dm-*
> target listed in these and i am curious as to what are the differences
> between what goes into these arrays and what does not.

These are only for the targets and services provided by the DM core
(dm-mod.ko went built as a module).

  reply	other threads:[~2014-05-07 13:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-07  4:45 if i create a new dm target type, do i need to add its init to the _inits[] and its exit to the _exits[]? John Utz
2014-05-07 13:09 ` Mike Snitzer [this message]
2014-05-07 16:00   ` John Utz

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=20140507130946.GA29851@redhat.com \
    --to=snitzer@redhat.com \
    --cc=John.Utz@wdc.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 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.