[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1300164733.28255.267.camel@haakon2.linux-iscsi.org>
Date: Mon, 14 Mar 2011 21:52:13 -0700
From: "Nicholas A. Bellinger" <nab@...ux-iscsi.org>
To: Jesper Juhl <jj@...osbits.net>
Cc: linux-scsi <linux-scsi@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
James Bottomley <James.Bottomley@...senPartnership.com>,
Christoph Hellwig <hch@....de>,
Mike Christie <michaelc@...wisc.edu>,
Hannes Reinecke <hare@...e.de>,
FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>,
Boaz Harrosh <bharrosh@...asas.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Douglas Gilbert <dgilbert@...erlog.com>
Subject: Re: [RFC-v2 12/12] iscsi-target: Add Makefile/Kconfig and update
TCM top level
On Tue, 2011-03-15 at 02:03 +0100, Jesper Juhl wrote:
> On Mon, 14 Mar 2011, Nicholas A. Bellinger wrote:
>
> > From: Nicholas Bellinger <nab@...ux-iscsi.org>
> >
> [...]
> > diff --git a/drivers/target/Makefile b/drivers/target/Makefile
> > index 60028fe..b038b7d 100644
> > --- a/drivers/target/Makefile
> > +++ b/drivers/target/Makefile
> > @@ -24,3 +24,4 @@ obj-$(CONFIG_TCM_PSCSI) += target_core_pscsi.o
> >
> > # Fabric modules
> > obj-$(CONFIG_TCM_LOOP_FABRIC) += tcm_loop/
> > +obj-$(CONFIG_ISCSI_TARGET) += iscsi/
> > diff --git a/drivers/target/iscsi/Kconfig b/drivers/target/iscsi/Kconfig
> > new file mode 100644
> > index 0000000..cc34243
> > --- /dev/null
> > +++ b/drivers/target/iscsi/Kconfig
> > @@ -0,0 +1,17 @@
> > +config ISCSI_TARGET
> > + tristate "Linux-iSCSI.org iSCSI Target Mode Stack"
> > + select CRYPTO
> > + select CRYPTO_CRC32C
> > + select CRYPTO_CRC32C_INTEL if X86
> > + help
> > + Say Y here to enable the ConfigFS enabled Linux-iSCSI.org iSCSI
> > + Target Mode Stack.
> > +
> > +if ISCSI_TARGET
> > +
> > +config ISCSI_TARGET_DEBUG
> > + bool "LIO-Target iscsi_debug.h ring buffer messages"
> > + help
> > + Say Y here to enable the legacy DEBUG_ISCSI macros in iscsi_debug.h
> > +
> > +endif
> [...]
>
> Perhaps this is a stupid question, but if these are "legacy" macros, why
> not save our users from having to deal with a new config option that is
> presumably going to go away again soon-ish and instead make those legacy
> macros go away sooner rather than later?
>
A fair point here. Perhaps calling them 'legacy' is a bit harsh, as
these are still useful for short-term v4.1 iSCSI target debugging
purposes. In the long run these do need to be converted to use debugfs
(along with the rest of drivers/target/ as well), but this is currently
a lower priority item on the TODO for the initial merge.
Best Regards,
--nab
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists