From: Pete Zaitcev <zaitcev@redhat.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: "Kristian Høgsberg" <krh@redhat.com>,
linux-kernel@vger.kernel.org, zaitcev@redhat.com
Subject: Re: Juju
Date: Thu, 25 Jan 2007 20:47:33 -0800 [thread overview]
Message-ID: <20070125204733.1ae70031.zaitcev@redhat.com> (raw)
In-Reply-To: <45B968E7.1070402@s5r6.in-berlin.de>
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
next prev parent reply other threads:[~2007-01-26 4:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 6:37 Juju Pete Zaitcev
2007-01-25 17:13 ` Juju Stefan Richter
2007-01-25 21:18 ` Juju Kristian Høgsberg
2007-01-25 23:38 ` Juju Pete Zaitcev
2007-01-26 2:35 ` Juju Stefan Richter
2007-01-26 4:01 ` Juju Kristian Høgsberg
2007-01-26 11:30 ` Juju Stefan Richter
2007-01-26 4:47 ` Pete Zaitcev [this message]
2007-01-26 10:53 ` Juju Stefan Richter
2007-01-26 6:47 ` Juju Greg KH
2007-01-26 19:51 ` Juju Kristian Høgsberg
2007-01-29 0:13 ` Juju Pete Zaitcev
2007-01-29 19:53 ` Juju Kristian Høgsberg
2007-01-29 20:22 ` Juju Pete Zaitcev
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=20070125204733.1ae70031.zaitcev@redhat.com \
--to=zaitcev@redhat.com \
--cc=krh@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.