From: Bart Van Assche <bart.vanassche@sandisk.com>
To: Yann Droneaud <ydroneaud@opteya.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Sagi Grimberg <sagig@mellanox.com>,
Sebastian Parschauer <sebastian.riemer@profitbricks.com>,
Brian King <brking@linux.vnet.ibm.com>,
Nathan Fontenot <nfont@linux.vnet.ibm.com>,
Tyrel Datwyler <tyreld@linux.vnet.ibm.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
linux-rdma <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH] IB/srp: Add 64-bit LUN support
Date: Tue, 10 Feb 2015 12:41:22 +0100 [thread overview]
Message-ID: <54D9EE62.1010304@sandisk.com> (raw)
In-Reply-To: <1423556633.32606.7.camel@opteya.com>
Hello Yann,
On 02/10/15 11:13, Yann Droneaud wrote:
> Le lundi 02 février 2015 à 18:21 +0100, Bart Van Assche a écrit :
>> The largest LUN number that has been tested is 0xd2003fff00000000.
>>
>> Checked the following structure sizes with gdb:
>> * sizeof(struct srp_cmd) = 48
>> * sizeof(struct srp_tsk_mgmt) = 48
>> * sizeof(struct srp_aer_req) = 36
>
> You can use 'pahole' tool to retrieve the size (and layout) of any
> data structure from a .o object file.
Thanks, I will have a look at that tool.
>> The ibmvscsi changes have been compile tested only (on a PPC system).
>
> The changelog lack of any information about the purpose of 64bit LUNs.
> Please detail a bit why and how.
You might have missed Hannes' patch series through which 64-bit LUN
support was added in the SCSI core and in most SCSI LLD drivers. The
description of one of the patches in that series reads as follows:
"The SCSI standard defines 64-bit values for LUNs, and large arrays
employing large or hierarchical LUN numbers become more and more
common.
So update the linux SCSI stack to use 64-bit LUN numbers."
Is it OK for you if I resend this patch with that text added in the
patch description ?
Bart.
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-02-10 11:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 17:21 [PATCH] IB/srp: Add 64-bit LUN support Bart Van Assche
[not found] ` <54CFB228.4070208-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2015-02-09 16:39 ` Hannes Reinecke
2015-02-10 8:23 ` Yann Droneaud
2015-02-10 11:41 ` Bart Van Assche [this message]
[not found] ` <54D9EE62.1010304-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2015-02-10 13:00 ` Yann Droneaud
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=54D9EE62.1010304@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=brking@linux.vnet.ibm.com \
--cc=hch@infradead.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nfont@linux.vnet.ibm.com \
--cc=sagig@mellanox.com \
--cc=sebastian.riemer@profitbricks.com \
--cc=tyreld@linux.vnet.ibm.com \
--cc=ydroneaud@opteya.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;
as well as URLs for NNTP newsgroup(s).