public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Andy Grover <agrover@redhat.com>
Cc: target-devel <target-devel@vger.kernel.org>,
	linux-rdma <linux-rdma@vger.kernel.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	Roland Dreier <roland@kernel.org>,
	Or Gerlitz <ogerlitz@mellanox.com>,
	Alexander Nezhinsky <alexandern@mellanox.com>
Subject: Re: [RFC 01/11] iscsi-target: Add iscsit_transport API template
Date: Fri, 22 Mar 2013 15:29:59 -0700	[thread overview]
Message-ID: <1363991399.30339.22.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <514C9386.4080606@redhat.com>

On Fri, 2013-03-22 at 10:23 -0700, Andy Grover wrote:
> On 03/07/2013 05:45 PM, Nicholas A. Bellinger wrote:
> > From: Nicholas Bellinger <nab@linux-iscsi.org>
> >
> > Add basic struct iscsit_transport API template to allow iscsi-target for
> > running with external transport modules using existing iscsi_target_core.h
> > code.
> >
> > For all external modules, this calls try_module_get() and module_put()
> > to obtain + release an external iscsit_transport module reference count.
> >
> > Also include the iscsi-target symbols necessary in iscsi_transport.h to
> > allow external transport modules to function.
> >
> > Signed-off-by: Nicholas Bellinger <nab@linux-iscsi.org>
> > ---
> >   drivers/target/iscsi/Makefile                 |    3 +-
> >   drivers/target/iscsi/iscsi_target_transport.c |   57 ++++++++++++++++++
> >   include/target/iscsi/iscsi_transport.h        |   77 +++++++++++++++++++++++++
> >   3 files changed, 136 insertions(+), 1 deletions(-)
> >   create mode 100644 drivers/target/iscsi/iscsi_target_transport.c
> >   create mode 100644 include/target/iscsi/iscsi_transport.h
> >
> > diff --git a/drivers/target/iscsi/Makefile b/drivers/target/iscsi/Makefile
> > index 5b9a2cf..13a9240 100644
> > --- a/drivers/target/iscsi/Makefile
> > +++ b/drivers/target/iscsi/Makefile
> > @@ -15,6 +15,7 @@ iscsi_target_mod-y +=		iscsi_target_parameters.o \
> >   				iscsi_target_util.o \
> >   				iscsi_target.o \
> >   				iscsi_target_configfs.o \
> > -				iscsi_target_stat.o
> > +				iscsi_target_stat.o \
> > +				iscsi_target_transport.o
> >
> >   obj-$(CONFIG_ISCSI_TARGET)	+= iscsi_target_mod.o
> > diff --git a/drivers/target/iscsi/iscsi_target_transport.c b/drivers/target/iscsi/iscsi_target_transport.c
> > new file mode 100644
> > index 0000000..4ffd965
> > --- /dev/null
> > +++ b/drivers/target/iscsi/iscsi_target_transport.c
> > @@ -0,0 +1,57 @@
> > +#include <linux/spinlock.h>
> > +#include <linux/list.h>
> > +#include <target/iscsi/iscsi_transport.h>
> > +
> > +static LIST_HEAD(g_transport_list);
> > +static DEFINE_MUTEX(transport_mutex);
> > +
> > +struct iscsit_transport *iscsit_get_transport(int type)
> > +{
> > +	struct iscsit_transport *t;
> > +
> > +	mutex_lock(&transport_mutex);
> > +	list_for_each_entry(t, &g_transport_list, t_node) {
> > +		if (t->transport_type == type) {
> > +			if (t->owner && !try_module_get(t->owner)) {
> > +				t = NULL;
> > +			}
> > +			mutex_unlock(&transport_mutex);
> > +			return t;
> > +		}
> > +	}
> > +	mutex_unlock(&transport_mutex);
> > +
> > +	return NULL;
> > +}
> > +EXPORT_SYMBOL(iscsit_get_transport);
> > +
> > +void iscsit_put_transport(struct iscsit_transport *t)
> > +{
> > +	if (t->owner)
> > +		module_put(t->owner);
> > +}
> > +EXPORT_SYMBOL(iscsit_put_transport);
> > +
> > +int iscsit_create_transport(struct iscsit_transport *t)
> > +{
> > +	INIT_LIST_HEAD(&t->t_node);
> > +
> > +	mutex_lock(&transport_mutex);
> > +	list_add_tail(&t->t_node, &g_transport_list);
> > +	mutex_unlock(&transport_mutex);
> > +
> > +	printk("Created iSCSI transport: %s\n", t->name);
> > +
> > +	return 0;
> > +}
> > +EXPORT_SYMBOL(iscsit_create_transport);
> > +
> > +void iscsit_destroy_transport(struct iscsit_transport *t)
> > +{
> > +	mutex_lock(&transport_mutex);
> > +	list_del(&t->t_node);
> > +	mutex_unlock(&transport_mutex);
> > +
> > +	printk("Destroyed iSCSI transport: %s\n", t->name);
> > +}
> 
> I don't think create/destroy are the right names to use here - I suggest 
> register/unregister or something like that?
> 

Fair enough.  Renamed to register/unregister in the forth-coming RFC-v2

> Please also make sure to turn those printks in to pr_something() for the 
> final version.
> 

Done.

Thanks,

--nab



  reply	other threads:[~2013-03-22 22:30 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-08  1:45 [RFC 00/11] Add support for iSCSI Extentions for RDMA (ISER) target Nicholas A. Bellinger
2013-03-08  1:45 ` [RFC 01/11] iscsi-target: Add iscsit_transport API template Nicholas A. Bellinger
2013-03-08  4:14   ` Roland Dreier
     [not found]     ` <CAG4TOxM=PDYXCAMNdRx629aAP+XF7oZmykg0k4b+a688PzzayA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-03-08  6:02       ` Nicholas A. Bellinger
2013-03-08 16:59         ` Roland Dreier
2013-03-08 12:36     ` Or Gerlitz
2013-03-08 21:26       ` Nicholas A. Bellinger
2013-03-22 17:23   ` Andy Grover
2013-03-22 22:29     ` Nicholas A. Bellinger [this message]
2013-03-08  1:45 ` [RFC 02/11] iscsi-target: Initial traditional TCP conversion to iscsit_transport Nicholas A. Bellinger
2013-03-22 17:23   ` Andy Grover
2013-03-22 22:38     ` Nicholas A. Bellinger
2013-03-08  1:45 ` [RFC 03/11] iscsi-target: Add iser-target parameter keys + setup during login Nicholas A. Bellinger
2013-03-22 17:23   ` Andy Grover
2013-03-22 22:57     ` Nicholas A. Bellinger
2013-03-08  1:45 ` [RFC 05/11] iscsi-target: Refactor RX PDU logic + export request PDU handling Nicholas A. Bellinger
     [not found]   ` <1362707116-31406-6-git-send-email-nab-IzHhD5pYlfBP7FQvKIMDCQ@public.gmane.org>
2013-03-22 17:23     ` Andy Grover
2013-03-22 23:09       ` Nicholas A. Bellinger
     [not found] ` <1362707116-31406-1-git-send-email-nab-IzHhD5pYlfBP7FQvKIMDCQ@public.gmane.org>
2013-03-08  1:45   ` [RFC 04/11] iscsi-target: Add per transport iscsi_cmd alloc/free Nicholas A. Bellinger
2013-03-08 14:29     ` Asias He
2013-03-08 20:47       ` Nicholas A. Bellinger
     [not found]     ` <1362707116-31406-5-git-send-email-nab-IzHhD5pYlfBP7FQvKIMDCQ@public.gmane.org>
2013-03-22 17:23       ` Andy Grover
2013-03-22 22:59         ` Nicholas A. Bellinger
2013-03-08  1:45   ` [RFC 06/11] iscsi-target: Refactor TX queue logic + export response PDU creation Nicholas A. Bellinger
2013-03-08  1:45 ` [RFC 07/11] iscsi-target: Add iser network portal attribute Nicholas A. Bellinger
2013-03-08  1:45 ` [RFC 08/11] iser-target: Add base + proto includes Nicholas A. Bellinger
2013-03-08  1:45 ` [RFC 09/11] iser-target: Add logic for verbs Nicholas A. Bellinger
2013-03-14 11:19   ` Or Gerlitz
     [not found]   ` <1362707116-31406-10-git-send-email-nab-IzHhD5pYlfBP7FQvKIMDCQ@public.gmane.org>
2013-03-14 11:42     ` Or Gerlitz
2013-03-08  1:45 ` [RFC 10/11] iser-target: Add logic for core Nicholas A. Bellinger
2013-03-14 11:08   ` Or Gerlitz
2013-03-14 11:58   ` Or Gerlitz
2013-03-08  1:45 ` [RFC 11/11] iser-target: Add Makefile + Kconfig Nicholas A. Bellinger
2013-03-14  8:17 ` [RFC 00/11] Add support for iSCSI Extentions for RDMA (ISER) target Or Gerlitz

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=1363991399.30339.22.camel@haakon2.linux-iscsi.org \
    --to=nab@linux-iscsi.org \
    --cc=agrover@redhat.com \
    --cc=alexandern@mellanox.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=ogerlitz@mellanox.com \
    --cc=roland@kernel.org \
    --cc=target-devel@vger.kernel.org \
    /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