SAS vs FC

7/12/2011

Hitting on the comparison between FC and SAS. It was reallydifficult in the beginning – so many concepts I know about, or heard about butjust don’t really understand. And so many protocols. FC has at least 7– it issupposed to have only five, but I don’t know where the FC-AL protocol come from,well, should be a sub-protocol of FC-2. And so is the FC-SW protocol.

Also I need to know SAS. Its protocol looks not many – allthree sub-protocols are incorporated into the SAS standard. But I don’t knowwhy after SAS 2.1, T10 divided the protocol into two documents: SAS, and SASProtocol Layer. Both’s names are greatly ambiguous – could it be that T10 folksthought a single SAS protocol looks too simple hence tried to make it lookcomplicated?

Anyway, comparing studying SCSI protocol, FC and SAS aremuch easier – they are just carrier protocols. FC puts a lot controllingmechanism into its frame header by which it can play a lots of tricks whichbring it the reputation of high reliability and high performance but also makeit unfamiliar to most IT ppl. SAS is a even simpler protocol. Like FC, It isalso a carrier layer dealing with the lower 4 layers of OSI model.

 

 

7/17/2011

Done the paper of FC vs SAS. Really tedious work – manythings I actually don’t have hands on experiences but have to dig in. althoughmy experience with hw, sw and sys seems not too low to understand the intentsthat the standard tries to express, but it is indeed a tiring work, and hard toremember for those unfamiliar stuff – even I kinda understood them at the timewriting the paper.

No sweet w/o sweat. Vice versa, if you spill your sweat in aproper way, you will be assured to get some sweet. So was my paper writing. Afterfinishing this battle, I found I gained much more sense about the protocols. Previouslyit is just hard for me to grab the essence of some descriptions in a groups ofassociated protocols. But now, after comparing quite a number of SAS and FCprotocols, as well as reading a bunch of articles, now I’ve got some feelingabout these bibles in technical territory. I guess a clergy could have thesimilar feeling when he starts to understand the bible bit by bit, day by day…

Now get to the tech stuff. The comparison shows FC is reallyat some inadvantageous position compared with SAS. The only aspect it beats SASis the overhead. I don’t know why SAS still sets  1024 as the limit for payload data. Whatcould be the problem if setting it to 2048? Below is from my paper:

“Since theFC_DATA Information Unit at FC-4 layer carrying the data requested by SCSI commandis directly mapped into the data field of FC-2 frame, the overhead of FC isjust the overhead of FC-2, which is calculated as below,

 

1 -2112/2148=1.78%

 

For SAS SSP,since the transport frame is encapsulated into the link layer, the calculationshould add up the overhead in both transport layer and link layer. Belowequation shows the calculation result.


  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
IDE(ATA):IDE(Integrated Drive Electronics)是一种接口标准,用于连接计算机主板和硬盘驱动器。它使用并行传输方式传输数据,速度较慢,最初用于连接传统的机械硬盘。由于技术限制,IDE 接口通常只能连接两个设备,传输速度有限。现在已被新一代接口取代,主要用于老式计算机和低性能设备。 SATA:SATA(Serial ATA)是一种用于连接计算机主板和硬盘驱动器的接口标准。它使用串行传输方式传输数据,速度较快。SATA 接口比 IDE 接口更先进,可以同时连接多个设备,每个设备都有自己的数据通道,相互之间不会互相干扰。现代计算机和硬盘驱动器通常都采用 SATA 接口。 SCSI:SCSI(Small Computer System Interface)是一种用于连接计算机和外部设备的接口标准。它采用并行传输方式,适用于高速数据传输和连接多个设备。SCSI 接口不仅可以连接硬盘驱动器,还可以连接打印机、光驱、磁带机等设备。然而,由于成本高昂和配置复杂,SCSI 接口在个人计算机领域的应用相对较少。 SASSAS(Serial Attached SCSI)是一种基于串行传输方式的SCSI接口标准。它继承了SCSI 接口的优点,提供高速数据传输和连接多个设备的能力。SAS 接口一般用于高性能服务器和存储设备,可以连接硬盘驱动器、磁带机、RAID 控制器等外部设备。 FCFC(Fibre Channel)是一种用于连接计算机和存储设备的接口标准。它使用光纤传输数据,可以提供高带宽和低延迟的数据传输速度。FC 接口常用于大型计算机环境,适用于存储网络和数据中心等场景。它可以连接硬盘阵列、光纤交换机、磁带库等外部设备。

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值