[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4C6EF67E.2060908@cs.wisc.edu>
Date: Fri, 20 Aug 2010 16:41:18 -0500
From: Mike Christie <michaelc@...wisc.edu>
To: FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
CC: nab@...ux-iscsi.org, linux-scsi@...r.kernel.org,
linux-kernel@...r.kernel.org, hch@....de, James.Bottomley@...e.de,
hare@...e.de
Subject: Re: Conversion of LIO-Target to use include/scsi/iscsi_proto.h defs
On 08/20/2010 02:32 AM, FUJITA Tomonori wrote:
> On Thu, 19 Aug 2010 15:45:47 -0700
> "Nicholas A. Bellinger"<nab@...ux-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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists