public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ashish A. Palekar" <apalekar@trebia.com>
To: Nitin Dhingra <nitin.dhingra@dcmtech.co.in>,
	linux-kernel@vger.kernel.org
Subject: Re: iSCSI support for Linux
Date: Tue, 30 Oct 2001 11:30:53 -0500	[thread overview]
Message-ID: <3BDED5BD.33C546EB@trebia.com> (raw)
In-Reply-To: <7FADCB99FC82D41199F9000629A85D1A0293A56F@DCMTECHDOM>

Nitin:

The Target side does support 64 bit LUNs - as recommended by SAM-2. The
SCSI Target Mid-level definition for a LUN is a u64. (Note: The SCSI
Target Mid-Level is a completely different entity than the SCSI
Initiator Mid-Level). The question that is up in the air is how to use
those 64 bits for a good target representation.

The other thing is that 64 bit LUNs are __VERY_RARELY__ used in the SCSI
world that I am familiar with. So unless you are in a highly specialized
operation where all 64 bits are important to you, you can get by with 32
bit LUNs.

On the Initiator side, the LUN issue also needs to be addressed by the
SCSI Initiator Mid-Level. The person to speak to in this regard would be
Eric Youngdale (eric@andante.org). In fact the LUN issue along with the
scan code are some of things on the SCSI todo list - the scan thing
being especially important if you are doing fibre channel to enable
dynamic target discovery.

Hope this helps
Ashish

Nitin Dhingra wrote:
> 
> Ashish,
>         I have seen your and other codes as well, I see that everybody's
> used lun field as supplied by
> middle layer right. No one is using 64-bit field acc. to SAM-2, but Linux
> Scsi Subsystem doesn't support 64-bit
> field it supports only 32-bit. Have you thought something about it and do
> you have any solution to this?
> 
> Kindly cc me as I am no longer in the mailing list.
> 
> regards,
> nitin

  reply	other threads:[~2001-10-30 16:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-30  4:28 iSCSI support for Linux Nitin Dhingra
2001-10-30 16:30 ` Ashish A. Palekar [this message]
2001-10-30 16:47   ` Matthew Jacob
  -- strict thread matches above, loose matches on Subject: below --
2001-10-29 19:29 Ashish A. Palekar
2001-10-29 21:42 ` Jeff V. Merkey

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=3BDED5BD.33C546EB@trebia.com \
    --to=apalekar@trebia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nitin.dhingra@dcmtech.co.in \
    /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