Date: Thu, 25 Jan 2007 20:47:33 -0800
From: Pete Zaitcev <zaitcev@redhat.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Kristian =?UTF-8?B?SMO4Z3NiZXJn?= <krh@redhat.com>,
       linux-kernel@vger.kernel.org, zaitcev@redhat.com
Subject: Re: Juju
Message-Id: <20070125204733.1ae70031.zaitcev@redhat.com>
In-Reply-To: <45B968E7.1070402@s5r6.in-berlin.de>
References: <20070124223745.33278eb4.zaitcev@redhat.com>
	<45B91EAB.9080004@redhat.com>
	<20070125153824.8d7f50c5.zaitcev@redhat.com>
	<45B968E7.1070402@s5r6.in-berlin.de>
Organization: Red Hat, Inc.
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1111
Lines: 27

On Fri, 26 Jan 2007 03:35:19 +0100, Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:

> The fundamental thing about SBP-2 is that ORBs ( = SCSI command blocks
> plus SBP-2 header) and data buffers all reside in the memory of the
> initiator (or of a 3rd party on the FireWire bus).

I recognize the concept, I worked with SRP in Infiniband a bit.

> The target wrote an SBP-2 status block into our memory. The status block
> contains the FireWire bus address of the ORB to which it belongs. [...]

I see. SRP has a more flexible tag which can be used to look up
the just completed command more effectively. But if we only submit
one, it's a moot point of course.

> [...] Since there aren't many
> mapped ORBs per target, a linked list is a reasonable data structure to
> search over.

Righto. I'm used to having thousands of oustanding commands in arrays.

-- Pete
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/