All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michaelc@cs.wisc.edu>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: jayamohank@serverengines.com, linux-scsi@vger.kernel.org,
	James.Bottomley@suse.de, open-iscsi@googlegroups.com
Subject: Re: [PATCH 2/2] RFC: The be2iscsi driver support for bsg
Date: Thu, 18 Mar 2010 16:02:52 -0500	[thread overview]
Message-ID: <4BA294FC.3030400@cs.wisc.edu> (raw)
In-Reply-To: <20100318225808Z.fujita.tomonori@lab.ntt.co.jp>

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.

So the approach using a common struct/cmd is ok with me, and if we can 
get a struct format works for everyone (qla4xxx, be2iscsi, cxgb4i) then 
I am fine.

  reply	other threads:[~2010-03-18 20:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-17 18:07 [PATCH 2/2] RFC: The be2iscsi driver support for bsg Jayamohan Kallickal
2010-03-18 13:58 ` FUJITA Tomonori
2010-03-18 21:02   ` Mike Christie [this message]
2010-03-18 23:10     ` FUJITA Tomonori
     [not found]       ` <20100319081016W.fujita.tomonori-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2010-03-19 12:56         ` James Smart
2010-03-22  8:57           ` FUJITA Tomonori
     [not found]             ` <20100322175704Y.fujita.tomonori-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2010-03-22 15:16               ` James Smart
2010-03-23 12:35                 ` FUJITA Tomonori
2010-03-19 21:11       ` Mike Christie

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=4BA294FC.3030400@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 \
    /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.