<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/1.5.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: SAS initiator and target mix</title>
	<link>http://storageadvisors.adaptec.com/2005/12/06/sas-initiator-and-target-mix/</link>
	<description>Storage Solutions for Real World IT Professionals</description>
	<pubDate>Thu, 18 Mar 2010 09:40:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.2</generator>

	<item>
 		<title>Comment on SAS initiator and target mix by: Tom</title>
		<link>http://storageadvisors.adaptec.com/2005/12/06/sas-initiator-and-target-mix/#comment-151</link>
		<pubDate>Fri, 24 Mar 2006 19:17:59 +0000</pubDate>
		<guid>http://storageadvisors.adaptec.com/2005/12/06/sas-initiator-and-target-mix/#comment-151</guid>
					<description>Joseph,

An HBA is allowed to straddle multiple SAS domains.  As in your example, an HBA could have a 4X connector to one domain and another 4X connect to a different domain.  Each of these domains can have &amp;#62;16K devices.

The limit of 100 disks is not a limit of expanders.  It's simply limited by the controller hardware.  One reason is that each disk typically has a structure defining that disk, and that structure is usually kept on-chip for performance reasons.  Also, each command to those disks has a structure.  All this adds up to signficant memory.  It appears that most of the chip vendors have chosen &quot;~100&quot; as a big enough disk count.

But eventually we'll see this change.  As SAS becomes more prevalent, I'm sure high-end SAS controllers will start to support a LOT more than 100 drives.

TT</description>
		<content:encoded><![CDATA[	<p>Joseph,</p>
	<p>An HBA is allowed to straddle multiple SAS domains.  As in your example, an HBA could have a 4X connector to one domain and another 4X connect to a different domain.  Each of these domains can have &gt;16K devices.</p>
	<p>The limit of 100 disks is not a limit of expanders.  It&#8217;s simply limited by the controller hardware.  One reason is that each disk typically has a structure defining that disk, and that structure is usually kept on-chip for performance reasons.  Also, each command to those disks has a structure.  All this adds up to signficant memory.  It appears that most of the chip vendors have chosen &#8220;~100&#8243; as a big enough disk count.</p>
	<p>But eventually we&#8217;ll see this change.  As SAS becomes more prevalent, I&#8217;m sure high-end SAS controllers will start to support a LOT more than 100 drives.</p>
	<p>TT
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on SAS initiator and target mix by: Joseph Sonnier</title>
		<link>http://storageadvisors.adaptec.com/2005/12/06/sas-initiator-and-target-mix/#comment-142</link>
		<pubDate>Tue, 14 Mar 2006 23:57:55 +0000</pubDate>
		<guid>http://storageadvisors.adaptec.com/2005/12/06/sas-initiator-and-target-mix/#comment-142</guid>
					<description>I have been confounded by this particular question.  If an HBA is limited to a 100 or so disk drives, can those disk exist in different Edge Domains?
So the typical SAS HBA has 4 or 8 ports - could it connect to 4 or 8 separate Edge Domains - as long as the total does not exceed the card's limit?  The SAS diagrams always show a host connected to the fan-out expander - which in turn connects multiple edge domains.  What is limiting the host from seeing only a 100 disk in the total SAS network?</description>
		<content:encoded><![CDATA[	<p>I have been confounded by this particular question.  If an HBA is limited to a 100 or so disk drives, can those disk exist in different Edge Domains?<br />
So the typical SAS HBA has 4 or 8 ports - could it connect to 4 or 8 separate Edge Domains - as long as the total does not exceed the card&#8217;s limit?  The SAS diagrams always show a host connected to the fan-out expander - which in turn connects multiple edge domains.  What is limiting the host from seeing only a 100 disk in the total SAS network?
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
