Warning: array_key_exists() [function.array-key-exists]: The second argument should be either an array or an object in /var/www/vhosts/webconnexxion.com/httpdocs/raid/includes/functions/sessions.php on line 88
Warning: array_key_exists() [function.array-key-exists]: The second argument should be either an array or an object in /var/www/vhosts/webconnexxion.com/httpdocs/raid/includes/functions/sessions.php on line 88
Warning: array_key_exists() [function.array-key-exists]: The second argument should be either an array or an object in /var/www/vhosts/webconnexxion.com/httpdocs/raid/includes/functions/sessions.php on line 88
Warning: array_key_exists() [function.array-key-exists]: The second argument should be either an array or an object in /var/www/vhosts/webconnexxion.com/httpdocs/raid/includes/functions/sessions.php on line 88
Warning: array_key_exists() [function.array-key-exists]: The second argument should be either an array or an object in /var/www/vhosts/webconnexxion.com/httpdocs/raid/includes/functions/sessions.php on line 88
Warning: array_key_exists() [function.array-key-exists]: The second argument should be either an array or an object in /var/www/vhosts/webconnexxion.com/httpdocs/raid/includes/functions/sessions.php on line 88
Warning: array_key_exists() [function.array-key-exists]: The second argument should be either an array or an object in /var/www/vhosts/webconnexxion.com/httpdocs/raid/includes/functions/sessions.php on line 88
Warning: array_key_exists() [function.array-key-exists]: The second argument should be either an array or an object in /var/www/vhosts/webconnexxion.com/httpdocs/raid/includes/functions/sessions.php on line 88
Warning: array_key_exists() [function.array-key-exists]: The second argument should be either an array or an object in /var/www/vhosts/webconnexxion.com/httpdocs/raid/includes/functions/sessions.php on line 88
Warning: array_key_exists() [function.array-key-exists]: The second argument should be either an array or an object in /var/www/vhosts/webconnexxion.com/httpdocs/raid/includes/functions/sessions.php on line 88 www.WebConneXXion.com | It s all about RAID
Warning: array_key_exists() [function.array-key-exists]: The second argument should be either an array or an object in /var/www/vhosts/webconnexxion.com/httpdocs/raid/includes/functions/sessions.php on line 88 My Account | Cart Contents | Checkout
De Small Computer Systems Interface bestaat sinds 1979 en is bedoeld om
meerdere, diverse soorten randapparatuur op ??n bus aan te sluiten. De SCSI bus
heeft sinds die tijd diverse ontwikkelingen doorlopen. Een verregaande
verhandeling is hier niet op zijn plaats maar een aantal belangrijke algemene
aspecten en een uiteenzetting van de gangbare SCSI varianten wel.
Het gebruik van de SCSI bus is gearbitreerd. Dat wil zeggen, de communicatie met
de randapparatuur wordt op basis van prioriteit toegewezen. Hierbij worden
commando"s en data apart behandeld in tegenstelling tot de parallel ATA bus
juist niet gebeurt. Daar moet de PC "wachten" op de complete afhandeling door
het device van het commando. Bij gebruik van meerdere devices op ??n bus kan
SCSI daarom betere I/O prestaties leveren t.o.v. IDE. Met name RAID systemen
maken hiervan gebruik. Data wordt verdeeld over de diverse harddisks. Deze disks
krijgen weliswaar stuk voor stuk de data aangeboden, maar zodra de data door de
buffer van disk #1 is opgenomen, geeft deze disk de bus vrij en gaat de data van
de buffer naar de interne disks worden geschreven. Gelijktijdig zal de SCSI
hostadapter de volgende harddisks data aanbieden. Zodra harddisk #1 intern klaar
is met schrijven, zal deze zich melden op de bus als zijnde gereed en kan het
volgende data block worden aangeboden.
LVD, HVD, Ultra, SCSI-3 ?
De verzameling van SCSI commando"s en de wijze waarop de data wordt verzonden
over de bus vormen het SCSI protocol. Dit protocol wordt aangeduid met SCSI-1,
SCSI-2, SCSI-3 en wordt vaak ten onrechte gebruikt om het type SCSI bus aan te
duiden. De SCSI bus kent benamingen zoals Fast-2, Ultra, Ultra2,Ultral?O en
Ultra320. De Fast-2 en Ultra uitvoeringen onderscheiden we in "Narrow" (8-bit
data pad), "Wide" (16-bit) en vervolgens in Single-Ended en High Voltage
Differential. Het verschil tussen Single-Ended en Differential is van
elektrische aard; bij Single-Ended bestaat een datalijn uit ??n signaal en een
massa, terwijl bij Differential er een plus", een "min" en een massa wordt
gebruikt. Met Differential SCSI kunnen langere kabels worden gebruikt, omdat
deze techniek veel minder gevoelig is voor storingen. De oude SCSI uitvoeringen
Fast-2 en Ultra kennen naast de standaard Single-ended uitvoeringen zgn. High
Voltage Differential uitvoeringen.
De Ultra2, Ultral160 en Ultra320 uitvoeringen zijn per definitie allemaal Low
Voltage Differential (LVD). Zoals de benaming al aangeeft werken deze met een
lage spanning op de bus. De LVD en HVD technologie?n zijn NIET uitwisselbaar
ofte combineren.
De Ultra SCSI bus heeft ruimte voor het aansluiten van maximaal 7 Narrow (8-bit)
of 15 Wide (16-bit) devices en de maximale data transfersnelheid bedraagt 20 en
40MB/seconde respectievelijk.
Ultra320 LVD SCSI
Ultra320 SCSI is de meest recente stap in de SCSI evolutie. Met de introductie
van diens voorganger Ultra 160 LVD SCSI, werden drie sleutel technologie?n
ge?ntroduceerd: Dual Edge Clocking, Domain Validation en Cyclic Redundancy Check
(CRC). Ultra320 SCSI biedt additionele technologie?n die, voor de eerste keer,
het SCSI protocol wijzigen, de overhead reduceren en daardoor de prestaties
verbeteren. Die wijzigingen maken veilige en betrouwbare datatransfers mogelijk
met snelheden tot 320 MB/sec. Ultra320 SCSI is niet voor ieder host platform
geschikt. Zo laat de 64-bit, 66MHz PCI-bus een maximale snelheid van
533MB/seconde toe en is ruimvoldoende om de 320MB/seconde stream aan te kunnen.
Een 64-bit/66MHz PCI kaart met twee Ultra320 kanalen zal deze bus echter al
kunnen verzadigen. Een 32-bit, 66Mhz bus zal maximaal 266MB/sec aan kunnen en is
daarom nog net ontoereikend voor ??n Ultra320 LVD kanaal. Verreweg de beste
systeem-bus voor Ultra320 is PCI-X die een bandbreedte van 1066MB/sec. heeft. De
nieuwe Ultra320 SCSI features zijn:
Double Transfer Speed: Spreekt eigenlijk voor zichzelf, een hogere (dubbel t.o.v.
Ultral60) kloksnelheid maakt hogere transfer snelheden mogelijk. Die hogere
snelheid is ook nodig als er meerdere devices zoals harddisks op ??n bus
aangesloten zijn omdat met de steeds sneller wordende disk drives de bus eerder
verzadigd raakt.
Packetized SCSI: Pakket gewijze communicatie verbetert het gebruik van de bus
door commando"s, data, status en messages te consolideren i.p.v. data en
overhead in verschillende bus fases te verdelen. Het gebruik van de bus is
daardoor optimaal omdat de overhead van commando"s en status zo min mogelijk de
bus in beslag neemt. Bij Ultral60 wordt alleen de data in de synchrone fase
overgedragen op 160MB/sec., terwijl de overhead op de veel tragere a-synchrone
(20 of40MB/sec) snelheid loopt.
- Quick Arbitration and Selection (QSA): Een methode om de bus toe te wijzen van
het ene naar het andere SCSI device zelf i.p.v. de controller. Ook deze techniek
opimaliseert het gebruik vande SCSI bus.
- Read and Write Data Streaming: Met deze techniek kunnen er meerdere data
pakketten achter elkaar verzonden worden zonder tussenkomst van commando s of
arbitrage.
- Flow Control: Is ook een optimalisatie techniek waarbij de overtollige data in
de pre-fetch buffers gewist wordt en plaats maakt voor de volgende data.
- Ultra320SCSI, de laatste parallel SCSI ? Net als bij Parallel ATA heeft de
ontwikkeling van de SCSI bus te kampen met de problematiek van een parallele
kabel interface.
De industrie buigt zich over de waarschijnlijk laatste parallel uitvoering
van de SCSI bus,
- Ultra640SCSI. Afhankelijk van de snelheid waarmee de logische voortzetting van SCSI, "Serial Attached SCSI" geaccepteerd zal worden gaat de Ultra640 al dan
niet meer in de markt verschijnen.
Meer info over SCSI: http://www.scsita.org
More efficient command and
data transfer with packetized SCSI
Packetized SCSI is a new protocol that, compared to non-packetized parallel
SCSI, provides a better way of transferring data between SCSI devices. By
using the SCSI bus" available bandwidth more efficiently, packetized SCSI
helps reduce protocol overhead to speed up communication between SCSI
devices. As a result, packetized SCSI is ideal for handling today"s
increased SCSI transfer speeds of 160 MB/sec and above. In addition,
packetized SCSI is compatible with non-packetized parallel SCSI to help
protect existing investments. Hitachi is now incorporating packetized SCSI
technology in the Hitachi Ultrastar*
hard disk drive family to help boost overall drive performance and
reliability.
A new way to reduce
protocol overhead during data transfers
Even though SCSI data transfer rates have progressed from the original 5 MB/sec
to the current 160 MB/sec, protocol overhead times have not changed during
that time. Today, with 160 MB/sec transfers and higher becoming much more
common, a significant limitation has arisen: too much of the SCSI bus
bandwidth is consumed by protocol overheads in these high-speed transfers.
To address this limitation, Hitachi is starting to implement packetized SCSI
technology as a way to improve data transfer in the Hitachi Ultrastar hard
disk drive family of products.
Packetized SCSI is an
innovative protocol that enables commands, messages, status, and data to be
transferred between SCSI devices by a more efficient method than
non-packetized parallel SCSI. For instance, non-packetized parallel SCSI
uses multiple phases to communicate different types of information between
SCSI devices: one for command information, two for messages, one for status,
and two for data. In contrast, packetized SCSI communicates all this
information by using only two data phases: one for each direction.
Although packetized SCSI
dramatically changes how protocol information moves between SCSI devices,
the change affects only the way information is transferred--not the content
or meaning of the information. In fact, packetized SCSI is compatible with
non-packetized parallel SCSI. As a result, packetized SCSI devices can
reside on the same bus as non-packetized SCSI devices. For example, one SCSI
device is designed to communicate with another SCSI device using packets
during one operation and then seamlessly switch to non-packetized operation
to communicate with yet another device. This happens in much the same way
SCSI devices switch data speeds depending on the speed negotiated between
the two devices.
A wide range of features
to increase transfer speed
Packetized SCSI offers a variety of new capabilities designed to increase
speed over non-packetized SCSI:
All protocol information
and data is transmitted at negotiated bus widths and speeds.
Multiple commands can be
issued in a single connection.
Data and status from
multiple commands can be transferred in a single connection.
Auto-sense provides an
automatic explanation of command failures.
All protocol information
and data is transmitted at negotiated bus widths and speeds: In
non-packetized parallel SCSI, all commands, messages, and status are
transferred through a narrow 8-bit bus at asynchronous data rates--the
slowest method of transferring information. In contrast, the actual data is
transferred at the fastest possible speed by using the widest bus at the
fastest synchronous data rate agreed to between two SCSI devices. As a
result, the time needed to transfer protocol information remains constant
even as data rates increase-and protocol data transfers increasingly consume
a larger percentage of the total command time.
With packetized SCSI, the
transfer of all commands, messages, and status is accomplished by using the
same agreed-to bus width and synchronous data rate as the data being
transferred. Thus, the time needed to transfer protocol information scales
down as synchronous data rates increase.
Multiple commands can be
issued in a single connection: With non-packetized parallel SCSI, only
one command can be issued each time SCSI devices start communicating. The
only way to receive another command is for the two devices to break the
connection and then establish a new connection. This means that each time a
SCSI device attempts to send a command, it must wait until the SCSI bus is
free, gain control of the SCSI bus, send the appropriate messages, and then
send a command.
With packetized SCSI, one
SCSI device can send multiple commands to another, because the command
identification and destination information are not part of the device
selection process. Instead, that information is sent before each command.
The device that attempts to send multiple commands needs only to wait for
the SCSI bus to be free and gain control once. This significantly reduces
the amount of time required for a SCSI device to issue multiple commands.
Data and status from
multiple commands can be transferred in a single connection: As is the
case with commands, non-packetized parallel SCSI cannot transfer data or
status for a new command without first disconnecting from the current
command (if there is one), waiting until the SCSI bus is free, gaining
control of the SCSI bus, and then sending the appropriate messages. (Non-
packetized parallel SCSI does allow data and status for a single command to
be sent during a single connection.)
With packetized SCSI, a
device can choose to send or receive data, and send status for any number of
commands. Again, packetized SCSI enables this because the command
identification and destination information are not part of the selection
process. Instead, that information is sent before each packet of data and
status. The device that attempts to send or receive data, or send status
needs only to wait for the SCSI bus to be free and gain control of it once.
This enables a more efficient use of the SCSI bus available bandwidth.
Auto-sense provides an
automatic explanation of command failures: When a command fails in
non-packetized SCSI, the device that originated the command must issue
another command to find out information about the failure. As a result, any
error recovery actions are delayed until that command has completed. When a
command fails in packetized SCSI, all available information about the
failure is returned as part of the status at the end of the failed command.
No additional commands are needed to determine the cause of the failure, so
error recovery actions can occur immediately.
The value of packetized
SCSI for high-speed transfers
The real value of packetized SCSI is based on the way SCSI handles its
protocol overhead. With non-packetized SCSI, protocol overhead times do not
change as data rates increase. This design was not much of a limitation for
data rates up to 80 MB/sec, but with 160 MB/sec transfers and above, too
much of the SCSI bus bandwidth is consumed by protocol overheads.
Consider the case of a
typical 8K-byte write command executed with non- packetized SCSI protocols
at different data rates. As shown in Figure 1, the percentage of the total
command time due to overhead is an acceptable less-than- 10 percent for data
transfer rates below 40 MB/sec. At 80 MB/sec, the overhead becomes
noticeable at 18 percent but is still within the acceptable range. At 160 MB/sec,
however, the overhead rises to 30 percent and starts becoming an issue.
Without a reliable solution to reduce protocol overhead, there is no added
benefit in implementing speeds above 160 MB/sec. Fortunately, packetized
SCSI provides a reliable solution to reduce protocol overheads to acceptable
levels.
The potential performance
improvement of using packetized SCSI
The performance improvement generated by using packetized SCSI can vary
significantly, depending on a variety of factors. The following examples are
designed to present the clearest picture of the differences between non-
packetized and packetized SCSI by eliminating most of the variables not
directly related to the actual transfer of data on the SCSI bus. These
examples assume that all the SCSI devices have all the data ready to
transfer and that there are no latency delays. As a result, the numbers
presented here are intended only to show the relative differences between
non-packetized and packetized SCSI--not the absolute throughput that could
be measured in an actual system.
Figure 2 shows the amount of
throughput in MB/sec that can be achieved by using packetized SCSI over
non-packetized SCSI when ten commands (four write and six read) are
transferred and executed with the SCSI bus running at various data rates.
Three different data transfer sizes are shown at each data rate. The top of
the lower (green) bar represents the maximum possible throughput that can be
achieved by using non-packetized SCSI. The top of the middle (blue) bar
represents the maximum possible throughput that can be achieved by using
packetized SCSI. The top of the top (red) bar represents the maximum
throughput that can be achieved if there were no protocol overhead. As
Figure 2 indicates, the relative improvement between non-packetized and
packetized SCSI is significant at data rates above 80 MB/sec.
Figure 2. Packetized SCSI vs. non-packetized SCSI performance
Figure 3 compares five
different workloads on a SCSI bus running at 160 MB/sec. It shows the amount
of throughput in MB/sec that can be achieved by using packetized SCSI over
non-packetized SCSI across a range of data transfer sizes from 512 bytes up
to 64 KB. The five workloads (shown from top to bottom) are:
Six reads and four writes
to a SCSI device that has a queue depth greater than ten (purple)
Six reads and four writes
to a SCSI device that has a queue depth of two (yellow)
Four writes to a SCSI
device that has a queue depth greater than four (blue)
One read (green)
One write (red)
Figure 3. Packetized SCSI vs. non-packetized SCSI performance at 160 MB/sec
Figure 3 shows that, across
all transfer sizes and workloads, packetized SCSI improves throughput over
non-packetized SCSI. The example in Figure 4 is identical to that in Figure
3, except that the SCSI bus is running at 320 MB/sec instead of 160 MB/sec.
It shows the same results as the example in Figure 3.
Figure 4. Packetized SCSI vs. non-packetized SCSI performance at 320 MB/sec
Packetized SCSI for
continued performance increases
Especially as SCSI data transfer speeds continue to rise beyond the 160 MB/sec
level, packetized SCSI technology provides a more efficient way to get the
most value from the higher rates. Hitachi plans to continue implementing
packetized SCSI in its Ultrastar family of hard disk drives. As a result,
these disk drives are designed to leverage the higher speeds to increase
overall drive performance and reliability.