public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michaelc@cs.wisc.edu>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: nab@linux-iscsi.org, linux-scsi@vger.kernel.org,
	linux-kernel@vger.kernel.org, hch@lst.de,
	James.Bottomley@suse.de, hare@suse.de
Subject: Re: Conversion of LIO-Target to use include/scsi/iscsi_proto.h defs
Date: Fri, 20 Aug 2010 16:41:18 -0500	[thread overview]
Message-ID: <4C6EF67E.2060908@cs.wisc.edu> (raw)
In-Reply-To: <20100820163058P.fujita.tomonori@lab.ntt.co.jp>

On 08/20/2010 02:32 AM, FUJITA Tomonori wrote:
> On Thu, 19 Aug 2010 15:45:47 -0700
> "Nicholas A. Bellinger"<nab@linux-iscsi.org>  wrote:
>
>> So, assuming that the conversion of all struct iscsi_init_* and struct
>> iscsi_target* to use include/scsi/iscsi_proto.h defs just involves
>> checking structure size and renaming the member use in
>> drivers/target/lio-target, would it be acceptable to do something like:
>>
>> /* iSCSI PDU Header */
>> struct iscsi_cmd {
>>          uint8_t opcode;
>>          uint8_t flags;
>>          __be16 rsvd2;
>>          uint8_t hlength;
>>          uint8_t dlength[3];
>>          uint8_t lun[8];
>>          itt_t    itt;   /* Initiator Task Tag */
>>          __be32 data_length;
>>          __be32 cmdsn;
>>          __be32 exp_statsn;
>>          uint8_t cdb[ISCSI_CDB_SIZE];    /* SCSI Command Block */
>>          /* Additional Data (Command Dependent) */
>> #ifdef ISCSI_TARGET_MODE
>>          __be32 header_digest;
>> #endif
>> };
>
> It's up to Mike but it looks hacky to me. struct iscsi_pdu is defined
> in the exact way as the spec does.
>
> I don't think that iscsi_proto.h conversion is a must for the mainline
> inclusion. I prefer to let it alone for now.

For the iscsi target, I think it is. For iscsi initiator drivers like 
bnx2i and be2iscsi we have made them convert from their headers to 
common linux ones including switching from driver specific defs to 
iscsi_proto.h.

For the merging of any target core stuff though, I do not think it is 
critical. The core target stuff does not need to be merged with a 
software iscsi target. They can do in at different times.

  parent reply	other threads:[~2010-08-20 21:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-19 22:45 Conversion of LIO-Target to use include/scsi/iscsi_proto.h defs Nicholas A. Bellinger
2010-08-20  7:32 ` FUJITA Tomonori
2010-08-20  9:14   ` Nicholas A. Bellinger
2010-08-20  9:41     ` FUJITA Tomonori
2010-08-20 10:02       ` Nicholas A. Bellinger
2010-08-20 10:43         ` FUJITA Tomonori
2010-08-20 10:57           ` Nicholas A. Bellinger
2010-08-20 21:41   ` Mike Christie [this message]
2010-08-20 23:55     ` Nicholas A. Bellinger
2010-08-22 19:06 ` Boaz Harrosh
2010-08-23 19:52   ` 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=4C6EF67E.2060908@cs.wisc.edu \
    --to=michaelc@cs.wisc.edu \
    --cc=James.Bottomley@suse.de \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nab@linux-iscsi.org \
    /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