All of lore.kernel.org
 help / color / mirror / Atom feed
From: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
To: nab@linux-iscsi.org
Cc: linux-scsi@vger.kernel.org, fujita.tomonori@lab.ntt.co.jp,
	brking@linux.vnet.ibm.com, lxie@us.ibm.com, rcjenn@us.ibm.com,
	michaelc@cs.wisc.edu, James.Bottomley@suse.de
Subject: Re: [PATCH] ibmvscsis: Move to struct ibmvscsis_vdev usage in fabric configfs handlers
Date: Tue, 2 Nov 2010 06:05:52 +0900	[thread overview]
Message-ID: <20101102060030Z.fujita.tomonori@lab.ntt.co.jp> (raw)
In-Reply-To: <1288480434-29670-1-git-send-email-nab@linux-iscsi.org>

On Sat, 30 Oct 2010 16:13:54 -0700
"Nicholas A. Bellinger" <nab@linux-iscsi.org> wrote:

> From: Nicholas Bellinger <nab@linux-iscsi.org>
> 
> This patch takes tomo-san original commit 94fdb0196151 and changes a handful
> of important items wrt to the fabric configfs logic.
> 
> Firstly, this patch introduces struct ibmvscsis_vdev and converts the
> VIO ibmvscsis_probe() and ibmvscsi_remove() callers to allocate/free
> struct ibmvscsis_vdev instead of the original usage of struct ibmvscsis_tpg
> which is intended to be allocated/freed respectively in ibmvscsis_make_tpg()
> and ibmvscsis_drop_tpg() fabric configfs handlers.

What happens if an initiator sends a crq command before an user
creates a tpg? Or what happens if an initiator sends a crq command
after removing a tpg?


> Secondly, this patch changes the metadata that is used to determine the
> fabric WWN and TPGT (collectively the TCM VIO SRP endpoint) layout for
> /sys/kernel/config/target/ibmvscsis/$WWN/tpgt_$TPGT/.  This patch will
> now use struct vio_dev->unit_address for $WWN, and dev_name(vio_dev->dev)
> for $TPGT.

I don't care much about this but vio_dev->unit_address ==
dev_name(vio_dev->dev), I think. See vio_register_device_node() in
arch/powerpc/kernel/vio.c. So it's odd a bit.

ibmvscsis model doesn't strictly follow the SRP SCSI model; no port,
wwpn, etc. 


>  The values passed in via configff for $WWN and $TPGT must match
> in ibmvscsis_make_tport() and ibmvscsis_make_tpg() against what has been
> automatically setup for each struct ibmvscsis_vdev in the VIO ibmvscsis_probe()
> callback.

As I said before, it's much better to create them automatically
instead of creating them via sysfs. The driver knows all nexuses to
handle.

  reply	other threads:[~2010-11-01 21:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-30 23:13 [PATCH] ibmvscsis: Move to struct ibmvscsis_vdev usage in fabric configfs handlers Nicholas A. Bellinger
2010-11-01 21:05 ` FUJITA Tomonori [this message]
2010-11-01 21:37   ` Nicholas A. Bellinger
2010-11-01 22:15     ` FUJITA Tomonori
2010-11-01 22:25       ` Nicholas A. Bellinger
2010-11-02  8:36         ` FUJITA Tomonori
2010-11-02 13:41       ` Brian King
2010-11-02 13:47       ` Brian King
2010-11-02 14:21         ` FUJITA Tomonori

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=20101102060030Z.fujita.tomonori@lab.ntt.co.jp \
    --to=fujita.tomonori@lab.ntt.co.jp \
    --cc=James.Bottomley@suse.de \
    --cc=brking@linux.vnet.ibm.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lxie@us.ibm.com \
    --cc=michaelc@cs.wisc.edu \
    --cc=nab@linux-iscsi.org \
    --cc=rcjenn@us.ibm.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.