public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michaelc@cs.wisc.edu>
To: Ravi Anand <ravi.anand@qlogic.com>
Cc: fujita.tomonori@lab.ntt.co.jp, jayamohank@serverengines.com,
	linux-scsi@vger.kernel.org, James.Bottomley@suse.de,
	open-iscsi@googlegroups.com
Subject: Re: FW: [PATCH 2/2] RFC: The be2iscsi driver support for bsg
Date: Mon, 22 Mar 2010 16:45:43 -0500	[thread overview]
Message-ID: <4BA7E507.1010605@cs.wisc.edu> (raw)
In-Reply-To: <20100319224835.GA31748@linux-qf4p>

On 03/19/2010 05:48 PM, Ravi Anand wrote:
>> On Thu, 18 Mar 2010 16:02:52 -0500
>> Mike Christie<michaelc@cs.wisc.edu>  wrote:
>>
>>> On 03/18/2010 08:58 AM, FUJITA Tomonori wrote:
>>>>
>>>> - You invent your hardware specific data structure for the simplest
>>>>     operation such as setting IP address.
>>>
>>> I think this is what Jay is not trying to do. I think the patch has some
>>> extra code like the ISCSI_BSG_HST_VENDOR parts that makes it confusing -
>>> it got me too. The ISCSI_BSG_HST_VENDOR code in be2iscsi looks like it
>>> is basically disabled (should remove for a formal patch when he sends
>>> for merging).
>>>
>>> It looks like there is a common struct iscsi_bsg_common_format that is
>>> getting passed around, and then in be2iscsi the driver is using that
>>> info to make a be2iscsi specific command. So scsi_transport_iscsi /
>>> ISCSI_SET_IP_ADDR / iscsi_bsg_common_format  gets translated by b2iscsi
>>> to b2iscsi / OPCODE_COMMON_ISCSI_NTWK_MODIFY_IP_ADDR / be_modify_ip_addr.
>>
>> Yeah, seems you are right. But looks like this patchset also adds the
>> vendor specific message support (ISCSI_BSG_HST_VENDOR)?
>>
.......

> Here's an early snapshot of the patch which we are working on to add
> the support using bsg vendor specific part - btw this is based on the previous
> iscsi bsg patch  and need to be synced up with what was posted recently.

Just to make sure we are all on the same page. Tomo's comments above 
means that for your comment about updating to the new code does not mean 
that you should just use the new HST_VENDOR cmd, and it does not mean 
that we only should use a common struct/cmd for net operations that Jay 
handled.

For other common operations we should do like Tomo suggested, and Jay 
started with the network stuff, and make common operations. You guys 
should also not feel like you have to use the format Jay posted with. We 
can modify it so it make sense for everyone.


> +	switch (msgcode) {
> +	case ISCSI_BSG_HST_VENDOR:
> +		rval = qla4xxx_process_vendor_specific(job);
> +		break;
> +	case ISCSI_BSG_HST_PING:
> +		rval = qla4xxx_ping(job);
> +		break;
> +	default:
> +		break;
> +	}
> +

      reply	other threads:[~2010-03-22 21:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-19 22:48 FW: [PATCH 2/2] RFC: The be2iscsi driver support for bsg Ravi Anand
2010-03-22 21:45 ` Mike Christie [this message]

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=4BA7E507.1010605@cs.wisc.edu \
    --to=michaelc@cs.wisc.edu \
    --cc=James.Bottomley@suse.de \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=jayamohank@serverengines.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=open-iscsi@googlegroups.com \
    --cc=ravi.anand@qlogic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox