public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Joel Becker <Joel.Becker@oracle.com>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: "Linux-iSCSI.org Target Dev"
	<linux-iscsi-target-dev@googlegroups.com>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	SCST-Devel <scst-devel@lists.sourceforge.net>
Subject: Re: ConfigFS + Target Mode Engine API discussion
Date: Wed, 10 Sep 2008 19:13:31 -0700	[thread overview]
Message-ID: <20080911021331.GA12902@mail.oracle.com> (raw)
In-Reply-To: <1221097366.27831.216.camel@haakon2.linux-iscsi.org>

On Wed, Sep 10, 2008 at 06:42:46PM -0700, Nicholas A. Bellinger wrote:
> So I am thinking about the following question:  What would be the
> preferred method for calling ct_group_ops->make_group() in order to
> create the $CONFIGFS/target/$FABRIC struct config_item directly from
> target_fabric_configfs_register() call?  From there, the config group
> hanging off $CONFIGFS/target/$FABRIC will be fabric dependent and
> providing their own groups, items, depends, from the passed *fabric_cit.
> How do I "simulate" a mkdir(2) configfs -> make_group() call coming from
> the fabric module itself..?   This would be assuming that both mkdir(2)

	That's precisely what you don't do with configfs.  It's a
defined "not to be done" thing.  So there's no preferred way, there's no
way at all.
	What you want do to is drive this from mkdir().  The
make_group() will look up the sub-module it needs and return the
appropriate item.

Joel


-- 

"The lawgiver, of all beings, most owes the law allegiance.  He of all
 men should behave as though the law compelled him.  But it is the
 universal weakness of mankind that what we are given to administer we
 presently imagine we own."
        - H.G. Wells

Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127

  reply	other threads:[~2008-09-11  2:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1221087547.27831.165.camel@haakon2.linux-iscsi.org>
     [not found] ` <20080910233107.GC23864@mail.oracle.com>
2008-09-11  1:42   ` ConfigFS + Target Mode Engine API discussion Nicholas A. Bellinger
2008-09-11  2:13     ` Joel Becker [this message]
2008-09-11  4:29       ` Nicholas A. Bellinger
2008-09-11  6:38         ` Joel Becker
2008-09-11  8:58           ` Nicholas A. Bellinger
2008-09-12 16:24             ` Nicholas A. Bellinger
2008-09-12 16:30               ` Nicholas A. Bellinger
2008-09-12 20:15             ` Joel Becker
2008-09-12 22:27               ` Nicholas A. Bellinger
2008-09-13  4:49                 ` Joel Becker
2008-09-13 19:22                   ` Nicholas A. Bellinger
2008-09-14  1:56                     ` Nicholas A. Bellinger

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=20080911021331.GA12902@mail.oracle.com \
    --to=joel.becker@oracle.com \
    --cc=linux-iscsi-target-dev@googlegroups.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nab@linux-iscsi.org \
    --cc=scst-devel@lists.sourceforge.net \
    /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