Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

What is NCQ (Native Command Queueing) and Why do we want it?

Command native ncq queueing
0
Posted

What is NCQ (Native Command Queueing) and Why do we want it?

0

Ans: This explaination is an excerpt from our Nforce 4 Tech Preview. One area that SCSI had over both parallel and SATA drives was Native Command Queuing (NCQ). Traditionally hard disks on the consumer desktop side process disk requests in a linear fashion. This can potentially be a very bad thing and to understand why, there has to be a basic understanding of the physical structure of a hard disk. Hard disks are made up of platters or disks, much like a compact disk. Each platter is divided into tracks which are concentric circles, tracks are divided into sectors. Each platter is read by one or more heads. Seeking data is fastest when the data resides on the same track. Moving between tracks is time consuming. Consider the case where there are three pieces of data, one on the outermost track, one on the inner most track and one on the outmost track. In a traditional hard disk, the data on the outer track would be read first, then the data on in the inner track second, and finally the

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.