| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <45B9DDB8.8010000@s5r6.in-berlin.de> Date: Fri, 26 Jan 2007 11:53:44 +0100 From: Stefan Richter <stefanr@...6.in-berlin.de> To: Pete Zaitcev <zaitcev@...hat.com> CC: Kristian Høgsberg <krh@...hat.com>, linux-kernel@...r.kernel.org Subject: Re: Juju Pete Zaitcev wrote: > On Fri, 26 Jan 2007 03:35:19 +0100, Stefan Richter <stefanr@...6.in-berlin.de> wrote: >> 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. And indeed, in the SBP-2 realm the ORB's address is actually the tag of the SCSI task. >> [...] 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. If I ever get to fix sbp2's handling of dynamically appended ORB lists, the next step would be to measure which queue depth is optimal for different hardware and different workloads. (Certainly much less than thousands for typical SBP-2 target(s)+initiator(s) setups.) -- Stefan Richter -=====-=-=== ---= ==-=- http://arcgraph.de/sr/ - 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