TWI824658B - Super speed universal serial bus control method and computer system therefor - Google Patents

Abstract

An interface controller having a memory space for storage of an endpoint list, and running a logic to dynamically add or delete the items in the endpoint list. The interface controller adds a first stream endpoint into the endpoint list when receiving a Not-Ready Packet from the first stream endpoint. A first stream state machine of the first stream endpoint switches to an idle state along with the sending of the Not-Ready Packet, waiting to enter a start-stream state. When the first stream endpoint has been recorded in the endpoint list, the interface controller skips switching the first stream state machine from the idle state to a prime-pipe state. The interface controller deletes the first stream endpoint from the endpoint list after all target transmissions of the first stream endpoint are completed.

Description

Ultra-high-speed universal serial bus control method and computer system for its implementation

The present invention relates to ultra-high-speed Universal Serial Bus (USB 3.0) control technology and supports UASP (Universal Serial Bus Attached Small Computer System Interface Protocol, USB Attached SCSI Protocol) devices.

USB 3.0 supports UASP devices, and the stream protocol (stream protocol) used allows the device to perform batch transfers, greatly improving system performance.

However, in order to optimize such batch transmission capabilities, considerable resources are required to manage the operating status of each endpoint on the device side. How to consume the least resources to achieve the highest performance is an important issue in this technical field.

This case provides an ultra-high-speed universal serial bus control technology.

A computer system implemented according to an embodiment of the present invention includes an interface controller. The interface controller has a cache space to store an endpoint list, and runs a logic to dynamically add and delete the endpoint list. When receiving a not-ready data packet sent by a first streaming endpoint, the interface controller records the first streaming endpoint in the endpoint list. A first streaming state machine of the first streaming endpoint switches to an idle state as the not-ready data packet is sent, waiting to enter a ready transmission state. When the endpoint list records the first streaming endpoint, the interface controller skips switching the first streaming state machine from the idle state to a total pipeline state. The interface controller deletes the first streaming endpoint from the endpoint list after all target transmissions of the first streaming endpoint are completed.

In one implementation, the interface controller checks the endpoint list when receiving an endpoint operation doorbell aimed at the first streaming endpoint. When it is detected that the first streaming endpoint has not been recorded in the endpoint list, the interface controller provides a notification packet to the first streaming endpoint, causing the first streaming state machine to enter the total pipeline state and issue the not ready packet to the interface controller.

In one implementation, the plurality of endpoint operation doorbells directed at the first streaming endpoint carry a plurality of tag values, indicating the target transmission of a plurality of segments of the first streaming endpoint. The first streaming state machine in the idle state switches to the ready transmission state according to a ready data packet sent by the first streaming endpoint corresponding to a target tag value, and further switches to a transmission state so that the target A segment of target transmission represented by the tag value is completed when the first streaming endpoint interacts with the interface controller, causing the first streaming state machine to switch back to the idle state. The interface controller determines whether any target transmission with a tag value associated with the first streaming endpoint has not been completed when the first streaming endpoint notifies that the segment of target transmission represented by the target tag value is completed. If all are completed, the interface controller deletes the first streaming endpoint from the endpoint list.

In one implementation, the interface controller further stores a task status note in the cache space to provide the first streaming endpoint with a first set of bits corresponding to a plurality of tag values. Each bit is normally in a first state. When the corresponding tag value is configured to mark a segment of target transmission, it is switched to a second state through the interface controller. It is not switched back to the first state until the segment of target transmission is completed. The interface controller determines that all target transmissions of the first streaming endpoint are completed based on the first group of bits that are in the first state.

There is also an implementation method to implement the concept of this project into an ultra-high-speed universal serial bus control method.

The following is a detailed description of the present invention with examples and accompanying drawings.

The following description sets forth various embodiments of the invention. The following description introduces the basic concepts of the invention and is not intended to limit the scope of the invention. The actual scope of the invention should be defined according to the scope of the patent application.

Figure 1 is a block diagram illustrating a computer system supporting UASP devices (USB 3.0 devices) according to an embodiment of the present invention. As shown in the figure, a host 100 can connect to multiple UASP devices.

Taking the USAP device 102 as an example, it has a command endpoint 104, a data-out endpoint 106, a data-in endpoint 108, and a status endpoint. (status endpoint)110. The command endpoint 104 allows the host 100 to implement bulk-out and non-streaming of commands. Different from the non-streaming design of the command endpoint 104, the data output endpoint 106 allows the host 100 to implement bulk-out and streaming of written data, while the data input endpoint 108 and the status endpoint 110 provide The host 100 implements bulk-in and streaming of reading data and device status. Streaming endpoints 106, 108, and 110 greatly increase the speed at which the host 100 reads and writes to the UASP device 102.

The host 100 runs an operating system (Operating System) 112 and operates a protocol driver (UAS driver) 114 to drive an interface driver (xHCI driver) 116, which in turn drives an interface controller (xHCI controller) 118 to control all UASP devices. The endpoints enable the state machine of each endpoint to operate. This case specifically introduces the control of streaming endpoints (including data output endpoint 106, data input endpoint 108, and a status endpoint 110); the interface controller 118 introduced can be implemented in a chipset. The computer system is interpreted as the interface controller 118, or a chipset including the interface controller 118, or the host 100 including the chipset, or the entire architecture of Figure 1.

Each streaming endpoint (data output endpoint 106, data input endpoint 108, and status endpoint 110) is equipped with a special stream state machine. Before a traditional streaming endpoint performs multi-segment target transmission, its streaming state machine may repeatedly switch between the main pipeline state PrimePipe and the idle state Idle. It takes a long time to return to the idle state Idle and wait to enter a preparatory transmission state StartStream. The interface controller 118 of this case manages an endpoint list 120 in a cache space 119, and directly marks the enabled streaming endpoint (recorded when it enters the idle state Idle), so that its streaming state machine no longer spends time in the total pipeline state PrimePipe And switch between idle states. In particular, the logic 122 run by the interface controller 118 has the ability to dynamically add and delete lists. Logic 122 may be implemented by circuitry and/or program code. Logic 122 not only adds newly enabled streaming endpoints to the endpoint list 120, but also removes streaming endpoints that complete all target transmissions from the endpoint list 120. In this way, the endpoint list 120 is moderately sized and cache space can be saved.

The endpoint list 120 may be stored in a plurality of registers. In one implementation, the first-class endpoint is recorded in the endpoint list 120 with 4B data, which may include the device number Slot# and the endpoint number EP# on the device.

In one implementation, the interface controller 118 further manages a task status note 124 in the cache space 119 . Logic 122 may refer to the task status annotation 124 to determine whether the target's streaming endpoint has completed all of its target transfers and can be removed from the endpoint list 120 . Task status notes 124 can also be stored in a temporary register.

Figure 2 shows the streaming state machine of the data input endpoint 108, including a disable state Disabled, a total pipeline state PrimePipe, an idle state Idle, a preparation transmission state StartStream, and a transmission state MoveData. The streaming data output endpoint 106 and the state endpoint 110 also have similar streaming state machines.

Traditional technology will repeatedly switch the streaming state machine between the total pipeline state PrimePipe and the idle state Idle when transmitting multiple segments of targets. With low hardware cost, this case successfully reduces the chance of the streaming state machine switching between the total pipeline state PrimePipe and the idle state Idle.

According to the design of this case, after the streaming endpoint sends a not-ready data packet NRDY, the streaming endpoint is recorded to control its streaming state machine to remain in the idle state as much as possible, waiting for the transmission of each target segment. Ready packet ERDY. The ready data packet ERDY will cause the streaming state machine to switch to the preparatory transmission state StartStream and the transmission state MoveData to complete the corresponding target transmission. When all target transmissions of this streaming endpoint are completed, the control of this streaming endpoint ends, making the control cost reasonable.

The following description takes the read operation as an example. Figure 3 illustrates the sequence of operations.

When the operating system 112 requests to read the UASP device 102, it will issue a read command (Data-in Transfer Command) 300 to inform the protocol driver 114 of a read address and a read size. The protocol driver 114 will send requests Itr(Stat), Itr(Data-in), and Otr(Cmd, CIU) to the interface driver 116, so that the interface driver 116 drives the interface controller 118. The requirements Itr (Stat) and Itr (Data-in) are used to set the host hardware, prepare to receive the status of the UASP device 102 response (eg, sensing information unit SIU), and read data. The requirement Otr(Cmd, CIU) is sent last and is used to transmit the command information unit (CIU).

How the data input endpoint 108 and the streaming state machine of the state endpoint 110 respond to the read command 300 are discussed below.

Data input endpoint 108 is discussed first. According to the request Itr(Data-in), the interface controller 118 generates a notification packet InAck(Data-in, Prime), causing the streaming state machine (Figure 2) of the data input pipeline (Data-in pipe) to enter the general pipeline state. PrimePipe notifies the UASP device 102 that the host 100 is ready to receive the read data responded by the UASP device 102. In response to the notification packet InAck (Data-in, Prime), the UASP device 102 responds with a not-ready data packet NRDY (Data-in, Prime), causing the streaming state machine to switch from the total pipeline state PrimePipe to the idle state Idle to facilitate switching. Prepare transmission status StartStream. Referring to Figure 1, the interface controller 118 uses logic 122 to add the data input endpoint 108 to the endpoint list 120 at this time, indicating that the streaming state machine of the data input endpoint 108 has passed the total pipeline state PrimePipe , and then set the idle state Idle.

This section discusses status endpoint 110. According to the request Itr(Stat), the interface controller 118 generates a notification packet InAck(Stat, Prime), causing the streaming state machine of the status pipe (similar to Figure 2) to enter the total pipeline state PrimePipe, and notifies the UASP device 102 The host 100 is ready to receive the status of the response from the UASP device 102 (eg, sensing information unit SIU). In response to the notification packet InAck(Stat, Prime), the UASP device 102 responds with a not-ready data packet NRDY(Stat, Prime), causing the streaming state machine to switch from the main pipeline state PrimePipe to the idle state Idle to facilitate switching to the ready transmission state StartStream. Referring to Figure 1, the interface controller 118 uses logic 122 to add the status endpoint 110 to the endpoint list 120 at this time, indicating that the streaming state machine of the status endpoint 110 has been processed by the total pipeline status PrimePipe, and then The setting of idle state Idle.

After the data input pipeline and the streaming state machine of the status pipeline are indeed in the idle state, according to the request Otr (Cmd, CIU), the interface controller 118 generates a command packet DP (Cmd, CIU) for transmission of the command information unit CIU. . After receiving the command packet DP (Cmd, CIU), the UASP device 102 responds with a notification packet ACK (Cmd), indicating that the command information unit CIU is successfully received. The interface controller 118 reports back to the interface driver 116 and the protocol driver 114 with a request OTc(Cmd). Since interface controller 118 is not a streaming endpoint, there is no need to populate endpoint list 120.

In particular, the data required to be read by the read instruction 300 can be divided into several sections for reading. For example, the 10K read data required by the read command 300 can be divided into 10 segments to read 1K each.

In the traditional design, the packet group 302 used for initial setting of the data input endpoint 108 and the status endpoint 110 will be repeated 10 times, and then the packet group 304 for command transmission will also be repeated 10 times. Packet groups 302/304 read in different segments are distinguished by different tag values. One implementation is to have the packet carry a stream ID (SID) whose value is set to the corresponding tag value. In particular, regarding the streaming endpoint, the repeatedly executed packet group 302 will cause the data input pipeline and the streaming state machine of the status pipeline to frequently switch between the total pipeline state PrimePipe and the idle state Idle.

However, using the technology of this case, the first time the packet group 302 is processed, the endpoint list 120 will be marked with the data input endpoint 108 and the status endpoint 110, indicating that the streaming state machine of the data input endpoint 108 and the status endpoint 110 has been completed. The setting of PrimePipe state and Idle state after passing through the pipeline. By querying the endpoint list 120, the interface controller 118 can avoid switching the streaming state machine of the data input endpoint 108 and the status endpoint 110 from the idle state Idle to the total pipeline state PrimePipe again. Therefore, the packet group 302 in this case will not be repeated, and its packets do not need to carry tag values. Only packet groups 304 for non-streaming endpoint communications are repeated. System performance is greatly improved.

After the above steps, each endpoint completes the pre-steps of reading data. The transmission of read data begins below.

The UASP device 102 generates a ready data packet ERDY (Data_in) to notify the interface controller 118 that the UASP device 102 is ready to transmit the read data of a certain tag value. According to the ready data packet ERDY (Data_in), the streaming state machine of the data input pipeline switches from the idle state Idle to the ready transmission state StartStream.

In response to the ready data packet ERDY (Data_in), the interface controller 118 sends a notification packet InAck (Data-in) to the UASP device 102 . According to the notification packet InAck (Data-in), the streaming state machine of the data input pipeline switches from the preparation transmission state StartStream to the transmission state MoveData and starts transmitting the read data. The UASP device 102 sends the data packet DP (Data-in).

Corresponding to the data packet DP (Data-in), the interface controller 118 sends a notification packet InAck (Data-in) to the UASP device 102, indicating that the packet for reading data is successfully received. After multiple pairs of packets DP (Data-in) and InAck (Data-in) interact, the read data transmission of the segment represented by the tag value is completed, and the interface controller 118 requests ITc (Data-in) and reports all the way to the interface driver 116 and protocol driver 114. The streaming state machine of the data input pipeline returns to the idle state Idle.

Taking the aforementioned 10 times of 1K segment reading as an example, the packet group 306 will be repeated 10 times, each corresponding to a tag value. Each packet is marked with a streaming code (SID) tag value.

In particular, after the read data of all segments has been transmitted (after the repeated packet group 306), the interface controller 118 will use logic 122 to delete the data input endpoint 108 from the endpoint list 120 to optimize the use of the cache space 119 . In one implementation, the 32-bit contents of the task status annotation 124 are provided for the data input endpoint 108, respectively corresponding to the transmission of read data of a tag value. The normal value of each bit is 1. A value of 0 means that the data read by the tag value has not yet been transmitted. If these 32 bits are all 1, the interface controller 118 determines that the read data of all segments of the data input endpoint 108 has been transmitted, and deletes the data input endpoint 108 from the endpoint list 120 .

After the read data transmission of all segments is completed, the UASP device 102 sends a ready data packet ERDY (Stat) to notify the interface controller 118 that the UASP device 102 is ready to transmit the sensing information unit SIU through the status pipeline. The ready data packet ERDY (Stat) also has a tag value. According to the ready data packet ERDY(Stat), the streaming state machine of the status pipeline switches from the idle state Idle to the ready transmission state StartStream.

Corresponding to the ready packet ERDY(Stat), the interface controller 118 sends a notification packet InAck(Stat) to the UASP device 102. According to the notification packet InAck(Stat), the streaming state machine of the status pipeline switches from the prepared transmission state StartStream to the transmission state MoveData, and generates a status packet DP(Stat, SIU) to transmit the sensing information unit SIU. Corresponding to the status packet DP(Stat, SIU), the interface controller 118 generates a notification packet ACK(Stat), indicating successful reception of the sensing information unit SIU. The streaming state machine of the state pipeline returns to the idle state Idle.

Taking the above-mentioned 10 times of reading 1K in each segment as an example, the packet group 308 will be repeated 10 times, each corresponding to a tag value. Each packet is marked with a streaming code (SID) tag value.

In particular, after all segmented device statuses have been transmitted (after repeating the packet group 308), the interface controller 118 will use logic 122 to delete the status endpoint 110 from the endpoint list 120 to optimize cache space 119 utilization. . In one implementation, the 32-bit contents of the task status annotation 124 are provided for the status endpoint 110, respectively corresponding to the status transmission of a tag value. Each bit is normally 1. A value of 0 indicates that the tag value status has not yet completed transmission. If these 32 bits are all 1, the interface controller 118 determines that the status transmission of all segments of the status endpoint 110 is completed, and deletes the status endpoint 110 from the endpoint list 120 .

The timing of the write operation initiated by the operating system 112 with a write command (Data-out Transfer Command) is similar to the timing of the read operation in Figure 3 . The small size cache space 119 is also used to achieve efficient operation of streaming endpoints (including the data output endpoint 106 and the status endpoint 110).

The above streaming endpoint operation concepts can be applied to various streaming endpoints, and are not limited to the data output endpoint 106, the data input endpoint 108, and the status endpoint 110.

Figure 4 is a flow chart illustrating an operation process of the interface controller 118 according to an embodiment of the present invention, which involves the operation of the logic 122 and explains how the interface controller 118 creates the endpoint list 120.

Step S402, the interface controller 118 receives the endpoint operation doorbell (EP doorbell, ITr, or Otr), which includes the device number Slot#, the endpoint number EP# on the device, and the tag value Stream# (# represents the number). In one implementation, the interface controller 118 can record the task status in the register 124 corresponding to the device number Slot# and the endpoint number EP# on the device, where the bit corresponding to the tag value Stream# is set to 0, representing the task to be completed. A segment of target transmission.

Step S404: According to the device number Slot# and the endpoint number EP# on the device, the interface controller 118 queries the endpoint list 120 to determine whether the streaming endpoint has been enabled (the total pipeline state PrimePipe and idle state Idle settings have been made) .

If the streaming endpoint currently required to operate has not been enabled and is not listed in the endpoint list 120, the interface controller 118 sends a notification packet in step S406 to switch the streaming state machine of the streaming endpoint to the main pipeline state PrimePipe. , then follow step S408 to receive the not-ready data packet NRDY responded by the streaming endpoint. At this time, the streaming state machine switches from the total pipeline state PrimePipe to the idle state Idle. The interface controller 118 loads the information of the streaming endpoint (including the device number Slot# and the endpoint number EP# on the device) into the endpoint list 120 in step S410, and records it as an enabled endpoint. The process ends.

On the contrary, if the streaming endpoint currently required to operate has been enabled and is listed in the endpoint list 120, the interface controller 118 skips steps S406 and S408, and the streaming state machine will no longer perform the pipeline state PrimePipe and the idle state Idle. switch. The streaming state machine was already in the idle state.

Figure 5 is a flow chart illustrating an operation process of the interface controller 118 according to an embodiment of the present case, which involves the operation of the logic 122 and explains how the interface controller 118 applies the endpoint list 120 and dynamically deletes the endpoints. List 120 content.

In step S502, the interface controller 118 receives a ready data packet ERDY from the streaming endpoint (labeled by the device number Slot# and the endpoint number EP# on the device), which contains a tag value Stream#. The streaming state machine enters the preparation transmission state StartStream and the transmission state MoveData along with the ready data packet ERDY, and performs a target transmission indicated by the tag value Stream#. At this time, the interface controller 118 receives the packet DP from the streaming endpoint in step S504. Step S506, the interface controller 118 learns that the streaming endpoint has completed the target transmission of the tag value Stream#, and records the task status 124 in the temporary register corresponding to the streaming endpoint, in which the bit settings corresponding to the tag value Stream# are set. 1. In step S508, the interface controller 118 determines whether the registers are all reset to the default value 1. If yes, it means that all target transmissions of the streaming endpoint are completed, and the interface controller 118 deletes the streaming endpoint from the endpoint list 120 in step S510. If not, the process ends without adjusting the endpoint list 120 .

In summary, this case allows streaming endpoints that have completed all target transmissions to be deleted from the endpoint list 120. In this way, the number of registers used by the endpoint list 120 can be greatly reduced. Taking the UASP device 102 as an example, the data output endpoint 106 and the data input endpoint 108 are not enabled at the same time. The endpoint list 120 only needs to provide at most two entries for the UASP device 102: the identification data output endpoint 106 and the status endpoint 110; or the identification data input endpoint 108 and the status endpoint 110. Compared with preparing buffers for each of the three streaming endpoints (data output endpoint 106, data input endpoint 108, and status endpoint 110) to record the transmission progress of the target transmission, this case dynamically adds and deletes the endpoint list. 120’s technology saves cache space by 119%.

In addition, taking a computer system that supports 32 UASP devices as an example, 32 UASP devices are usually not used at the same time. For example, most applications will only use 15 UASP devices. The endpoint list 120 is designed to handle 20 UASP devices, that is, it has a storage capacity of 20*2*4B (160B). Compared to preparing 32*3*4B (=384B) space for all streaming endpoints of all devices, the 160B endpoint list 120 is better in cache space utilization.

Table 1 below illustrates additions and deletions to the endpoint list 120. steps request/packet Slot# EP# Stream# Endpoint list 120 1 Endpoint operated doorbell 0x0E 0x04 0x02 null 2 InAck(Data-out, Prime) 0x0E 0x04 - null 3 NRDY(Data-out, Prime) 0x0E 0x04 - (E,4) 4 Endpoint operated doorbell 0x0E 0x07 0x02 (E,4) 5 InAck(Stat, Prime) 0x0E 0x07 - (E,4) 6 NRDY(Stat, Prime) 0x0E 0x07 - (E,4), (E,7) 7 Endpoint operated doorbell 0x0E 0x04 0x04 (E,4), (E,7) 8 Endpoint operated doorbell 0x0E 0x07 0x04 (E,4), (E,7) 9 Endpoint operated doorbell 0x0E 0x08 (E,4), (E,7) 10 Transfer writing data 0x0E 0x04 0x02 (E,4), (E,7) 11 Endpoint operated doorbell 0x0E 0x08 (E,4), (E,7) 12 Endpoint operated doorbell 0x0E 0x04 0x09 (E,4), (E,7) 13 Transmission status 0x0E 0x07 0x02 (E,4), (E,7) 14 Endpoint operated doorbell 0x0E 0x07 0x09 (E,4), (E,7) 15 Transfer and write data 0x0E 0x04 0x04 (E,4), (E,7) 16 Transmission status 0x0E 0x07 0x04 (E,4), (E,7) 17 Endpoint operated doorbell 0x0E 0x08 (E,4), (E,7) 18 Endpoint operated doorbell 0x0C 0x03 0x02 (E,4), (E,7) 19 InAck(Data-in, Prime) 0x0C 0x03 - (E,4), (E,7) 20 NRDY(Data-in, Prime) 0x0C 0x03 - (E,4), (E,7), (C,3) twenty one Endpoint operated doorbell 0x0C 0x07 0x02 (E,4), (E,7), (C,3) twenty two InAck(Stat, Prime) 0x0C 0x07 - (E,4), (E,7), (C,3) twenty three NRDY(Stat, Prime) 0x0C 0x07 - (E,4), (E,7), (C,3), (C,7) twenty four Endpoint operated doorbell 0x0C 0x03 0x05 (E,4), (E,7), (C,3), (C,7) 25 Transfer and write data 0x0E 0x04 0x09 (E,7), (C,3) , (C,7) 26 Endpoint operated doorbell 0x0C 0x07 0x05 (E,7), (C,3) , (C,7) 27 Transmission status 0x0E 0x07 0x09 (C,3) , (C,7) 28 Endpoint operated doorbell 0x0C 0x03 0x09 (C,3) , (C,7) 29 Endpoint operated doorbell 0x0C 0x07 0x09 (C,3) , (C,7) 30 Endpoint operated doorbell 0x0C 0x08 (C,3) , (C,7) 31 Endpoint operated doorbell 0x0C 0x08 (C,3) , (C,7) 32 Endpoint operated doorbell 0x0C 0x08 (C,3) , (C,7) 33 Transfer read data 0x0C 0x03 0x02 (C,3) , (C,7) 34 Transmission status 0x0C 0x07 0x02 (C,3) , (C,7) 35 Transfer read data 0x0C 0x03 0x05 (C,3) , (C,7) 36 Transmission status 0x0C 0x07 0x05 (C,3) , (C,7) 37 Transfer read data 0x0C 0x03 0x09 (C,7) 38 Transmission status 0x0C 0x07 0x09 null Table 1

Step 3. The streaming endpoint numbered 0x04 (data output endpoint) on device 0x0E is added to the endpoint list 120, which is (E, 4); in addition, it means that the streaming endpoint (E, 4) has a tag value The transmission of 0x02 is ready (Idle state), which also means that the streaming endpoint (E,4) is capable of handling the transmission requirements of tag values 0x04 (step 7) and 0x09 (step 12). The requirements of step 7 and step 12 do not trigger the switching of the total pipeline state PrimePipe and idle state Idle of the streaming state machine.

Step 6. The streaming endpoint (status endpoint) numbered 0x07 on device 0x0E is added to the endpoint list 120, which is (E,7); except that the streaming endpoint (E,7) has a tag value of 0x02 Being ready for transmission (Idle state) also means that the streaming endpoint (E,7) is capable of handling the transmission requirements of tag values 0x04 (step 8) and 0x09 (step 14). The requirements of step 8 and step 14 do not trigger the switching of the total pipeline state PrimePipe and idle state Idle of the streaming state machine.

Step 20, the streaming endpoint numbered 0x03 (data input endpoint) on device 0x0C is added to the endpoint list 120, which is (C, 3); in addition, it means that the streaming endpoint (C, 3) has a tag value The transmission of 0x02 is ready (Idle state), which also means that the streaming endpoint (C,3) is capable of handling the transmission requirements of tag values 0x05 (step 24) and 0x09 (step 28). The requirements of step 24 and step 28 do not trigger the switching of the total pipeline state PrimePipe and the idle state Idle of the streaming state machine.

Step 23, the streaming endpoint (status endpoint) numbered 0x07 on device 0x0C is added to the endpoint list 120, which is (C,7); in addition, it means that the streaming endpoint (C,7) has a label value of 0x02 The transmission is ready (Idle state), which also means that the streaming endpoint (C, 7) is capable of handling the transmission requirements of tag values 0x05 (step 26) and 0x09 (step 29). The requirements of step 26 and step 29 do not trigger the switching of the total pipeline state PrimePipe and the idle state Idle of the streaming state machine.

In particular, step 25, as the data output transmission with tag value 0x09 is completed, the data output endpoint numbered 0x04 on device 0x0E completes all tasks (the three data output transmissions marked with tag values 0x02, 0x04, and 0x09 are all completed) , record (E,4) is deleted from endpoint list 120 .

Step 27, as the status transmission of tag value 0x09 is completed, the status endpoint numbered 0x07 on device 0x0E completes all tasks (the three status transmissions marked by tag values 0x02, 0x04, and 0x09 are completed), and records (E,7 ) is removed from the endpoint list 120.

Step 37, as the data input and transmission of tag value 0x09 is completed, the data input endpoint numbered 0x03 on device 0x0C completes all tasks (the three data input and transmission segments marked by tag values 0x02, 0x05, and 0x09 are all completed), and records ( C,3) Delete from endpoint list 120 .

Step 38, as the status transmission of tag value 0x09 is completed, the status endpoint numbered 0x07 on device 0x0C completes all tasks (the three status transmissions marked by tag values 0x02, 0x05, and 0x09 are completed), and records (C,7 ) is removed from the endpoint list 120.

Table 1 shows the dynamic addition and deletion of the endpoint list 120. The interface controller 118 in this case obviously optimizes the cache space 119 occupied by the endpoint list 120.

This project proposes an efficient interface controller 118 for the ultra-high-speed Universal Serial Bus (USB 3.0).

The above concept can be implemented as an ultra-high-speed universal serial bus (USB 3.0) control method, including: storing an endpoint list 120 in a cache space 119, and running a logic 122 to dynamically add or delete the endpoint list 120; corresponding to a first stream A not-ready data packet NRDY is sent by the streaming endpoint, and the first streaming endpoint is recorded in the endpoint list 120, wherein a first streaming state machine of the first streaming endpoint is followed by the not-ready data packet After NRDY is issued, switch to an idle state Idle and wait to enter a preparatory transmission state StartStream; when the endpoint list 120 records the first streaming endpoint, skip switching the first streaming state machine from the idle state Idle. is a total pipeline state PipePrime; and after all target transmissions of the first streaming endpoint are completed, the first streaming endpoint is deleted from the endpoint list 120 .

In one embodiment, the control method further includes: operating a doorbell corresponding to the endpoint of the first streaming endpoint, checking the endpoint list 120; and after checking that the first streaming endpoint has not been recorded in the endpoint list 120. point, a notification packet InAck is provided to the first streaming endpoint, so that the first streaming state machine enters the total pipeline state PrimePipe and sends the not-ready data packet NRDY. The first streaming state machine is switched to the idle state Idle, and the first streaming endpoint is added to the endpoint list 120 .

In one implementation, the plurality of endpoint operation doorbells directed at the first streaming endpoint carry a plurality of tag values, indicating the target transmission of a plurality of segments of the first streaming endpoint. The first streaming state machine of the idle state Idle switches to the preparatory transmission state StartStream according to a ready data packet ERDY sent by the first streaming endpoint corresponding to a target tag value, and further switches to a transmission state MoveData. , completing a segment of target transmission represented by the target tag value, causing the first streaming state machine to switch back to the idle state Idle. The control method further determines whether any target transmission with a tag value associated with the first streaming endpoint has not been completed when the first streaming endpoint completes the target transmission represented by the target tag value; if all are completed, the The first streaming endpoint is deleted from the endpoint list 120 .

Although the present invention has been disclosed above in terms of preferred embodiments, they are not intended to limit the present invention. Anyone familiar with the technical field can make some changes and modifications without departing from the spirit and scope of the present invention. Therefore, the present invention The scope of protection shall be determined by the claims.

100:Host 102: UASP (Universal Serial Bus Attached Small Computer System Interface Protocol) device 104:Command endpoint 106: Data output endpoint 108: Data input endpoint 110: Status endpoint 112: Operating system (OS) 114: Protocol driver (UAS driver) 116:Interface driver (xHCI driver) 118: Interface controller (xHCI controller) 119: Cache space 120: Endpoint list 122: Logic of dynamic addition and deletion of lists 124:Task status notes 300: Read instructions 302, 304, 306, 308: Packet group Disabled: disabled state DP(Cmd, CIU), DP(Data-in), DP(Stat, SIU): command, data, status packet ERDY, ERDY(Data-in), ERDY(Stat): ready data packet Idle: idle state ITr(Stat), ITr(Data-in), OTr(Cmd, CIU), OTc(Cmd), ITc(Data-in), ITc(Stat, SIU): Requirements InACK(Data-in, Prime), InACK(Stat, Prime), ACK(Cmd), InACK(Data-in), InACK(Stat), ACK(Stat): notification packet MoveData:transmission status NRDY, NRDY(Data-in, Prime), NRDY(Stat, Prime): Not ready data packet PrimePipe:Total pipeline status S402…S410, S502…S510: steps StartStream: Preparatory transmission status

Figure 1 is a block diagram illustrating a computer system that supports UASP devices (USB 3.0 devices) according to an embodiment of the present invention; Figure 2 shows the streaming state machine of the data input endpoint 108; Figure 3 takes the read operation as an example to illustrate the operation sequence; Figure 4 is a flow chart illustrating an operation process of the interface controller 118 according to an embodiment of the present case, which involves the operation of the logic 122 and explains how the interface controller 118 creates the endpoint list 120; and Figure 5 is a flow chart illustrating an operation process of the interface controller 118 according to an embodiment of the present case, which involves the operation of the logic 122 and explains how the interface controller 118 applies the endpoint list 120 and dynamically deletes the endpoints. List 120 content.

without

100:Host

102: UASP (Universal Serial Bus Attached Small Computer System Interface Protocol) device

104:Command endpoint

106: Data output endpoint

108: Data input endpoint

110: Status endpoint

112: Operating system (OS)

114: Protocol driver (UAS driver)

116:Interface driver (xHCI driver)

118: Interface controller (xHCI controller)

119: Cache space

120: Endpoint list

122: Logic of dynamic addition and deletion of lists

124:Task status notes

Claims (20)

A computer system that realizes ultra-high-speed universal serial bus communication, including: an interface controller, which has a cache space to store an endpoint list, and runs a logic to dynamically add and delete the endpoint list, wherein: the interface controller receives When a first streaming endpoint sends a first not-ready data packet, the first streaming endpoint is recorded in the endpoint list; a first streaming state machine of the first streaming endpoint follows the first streaming endpoint. When the unready data packet is sent, it switches to an idle state and waits to enter a ready transmission state; when the endpoint list records the first streaming endpoint, the interface controller skips the first streaming state machine from the idle state. The state switches to a total pipeline state; the interface controller deletes the first streaming endpoint from the endpoint list after all target transmissions of the first streaming endpoint are completed; and the interface controller deletes the first streaming endpoint from the endpoint list after receiving each When the endpoint corresponding to a target transmission operates the doorbell, the endpoint list is checked to skip switching the first streaming state machine already contained in the endpoint list from the idle state to the total pipeline state, and instead causes the first streaming state machine to be switched to the general pipeline state. The first streaming state machine is in the idle state and waits to enter the preparatory transmission state, so as to switch to a transmission state to complete the corresponding target transmission of the segment. For example, request item 1 is a computer system for realizing ultra-high-speed universal serial bus communication, wherein: The interface controller checks the endpoint list when receiving the endpoint operation doorbell aimed at the first streaming endpoint, and when checking that the endpoint list has not recorded the first streaming endpoint, the interface controller The controller provides a notification packet to the first streaming endpoint, causing the first streaming state machine to enter the total pipeline state and send the first not-ready data packet to the interface controller. Such as claim 1, a computer system for realizing ultra-high-speed universal serial bus communication, wherein: operating a doorbell directed at a plurality of endpoints of the first streaming endpoint contains a plurality of tag values, indicating a plurality of the first streaming endpoints. Segment target transmission; the first streaming state machine in the idle state switches to the ready transmission state according to a ready data packet sent by the first streaming endpoint corresponding to a target tag value to further switch to the transmission state. , so that a segment of target transmission represented by the target tag value is completed under the interaction between the first streaming endpoint and the interface controller, causing the first streaming state machine to switch back to the idle state; and the interface controller is in the third When the first-stream streaming endpoint notifies the target segment represented by the target tag value that the transmission is completed, it determines whether any target transmission with the tag value associated with the first streaming endpoint is not completed. If all are completed, the interface controller transfers the first stream The endpoint is removed from the endpoint list. For example, in claim 1, the computer system for realizing ultra-high-speed Universal Serial Bus communication, wherein: the interface controller further stores a task status note in the cache space for the first stream. The endpoint provides a first group of bits corresponding to a plurality of tag values. Each bit is normally in a first state. When the corresponding tag value is configured to mark a target transmission, the interface controller switches to a second state until The segment of target transmission is completed before switching back to the first state; and the interface controller determines that all target transmissions of the first streaming endpoint are completed based on the first group of bits in the first state. For example, the computer system for realizing ultra-high-speed Universal Serial Bus communication in request item 1, wherein: when receiving a first endpoint operating the doorbell aimed at the first streaming endpoint, the interface controller checks that the endpoint list has not yet been Record the first streaming endpoint, so provide a notification packet to the first streaming endpoint, so that the first streaming state machine enters the total pipeline state, and sends the first not-ready data packet to the interface controller, so that the first streaming endpoint The interface controller records the first streaming endpoint in the endpoint list, and switches the first streaming state machine to the idle state; and aligns the first endpoint of the first streaming endpoint to operate the doorbell carrying a The first tag value indicates a first target transmission of the first streaming endpoint. For example, the computer system for realizing ultra-high-speed Universal Serial Bus communication in claim 5, wherein: when receiving a doorbell operation from a second endpoint aimed at the first streaming endpoint, the interface controller checks the endpoint list record With the first streaming endpoint, the interface controller skips switching the first streaming state machine from the idle state to the total pipeline state; and The second endpoint operating doorbell aligned with the first streaming endpoint carries a second tag value indicating a second target transmission of the first streaming endpoint. As claimed in claim 6, the computer system for realizing ultra-high-speed Universal Serial Bus communication, wherein: as the first streaming endpoint sends a ready data packet corresponding to the first tag value, the first streaming state machine changes from the idle state Entering the preparatory transmission state; the interface controller sends another notification packet in response to the ready data packet of the first tag value, causing the first streaming state machine to switch from the preparatory transmission state to the transmission state, causing the first streaming The endpoint interacts with the interface controller to complete the first target transmission; and after completing the first target transmission, the first streaming state machine returns to the idle state, and the interface controller determines that the first streaming endpoint is still in the idle state. If the second target transmission is not realized, the endpoint list maintains the record of the first streaming endpoint. As claimed in claim 7, the computer system for realizing ultra-high-speed universal serial bus communication, wherein: as the first streaming endpoint sends a ready data packet corresponding to the second tag value, the first streaming state machine changes from the idle state Entering the preparatory transmission state; the interface controller sends another notification packet in response to the ready data packet of the second tag value, causing the first streaming state machine to switch from the preparatory transmission state to the transmission state, causing the first streaming The endpoint interacts with the interface controller to complete the second target transmission; and After completing the second target transmission, the first streaming state machine returns to the idle state, and the interface controller determines that the first streaming endpoint has no target transmission to complete, and removes the first streaming endpoint from the endpoint. List delete. For example, the computer system for realizing ultra-high-speed Universal Serial Bus communication of claim 6, wherein: when receiving a third endpoint operating the doorbell aimed at a second streaming endpoint, the interface controller checks the endpoint list The second streaming endpoint has not yet been recorded, and another notification packet is provided to the second streaming endpoint, so that a second streaming state machine of the second streaming endpoint enters the total pipeline state and issues a second The not-ready data packet is sent to the interface controller, causing the interface controller to record the second streaming endpoint in the endpoint list, and causing the second streaming state machine to send out the second not-ready data packet. , switch to the idle state, and wait to enter the preparatory transmission state. For example, the computer system for realizing ultra-high-speed Universal Serial Bus communication in request item 9, wherein: when the endpoint list records the second streaming endpoint, the interface controller skips switching the second streaming state machine from the The idle state is switched to the total pipeline state; and the interface controller deletes the second streaming endpoint from the endpoint list after all target transmissions of the second streaming endpoint are completed. An ultra-high-speed universal serial bus control method includes: storing an endpoint list in a cache space, and running a logic to dynamically add and delete the endpoint list; Corresponding to a first not-ready data packet sent by a first streaming endpoint, the first streaming endpoint is recorded in the endpoint list, wherein a first streaming state machine of the first streaming endpoint follows the After the first unready data packet is sent, it switches to an idle state and waits to enter a ready transmission state; when the first streaming endpoint is recorded in the endpoint list, the first streaming state machine is skipped from the idle state. Switch to a total pipeline state; and after all target transmissions of the first streaming endpoint are completed, delete the first streaming endpoint from the endpoint list; wherein the ultra-high-speed universal serial bus control method is received When operating the doorbell on each endpoint corresponding to a segment of target transmission, the endpoint list is checked to skip switching the first streaming state machine already contained in the endpoint list from the idle state to the total pipeline state, and instead The first streaming state machine is placed in the idle state and waits to enter the preparatory transmission state, so as to switch to a transmission state to complete the corresponding target transmission. For example, the ultra-high-speed universal serial bus control method of claim 11 further includes: operating a doorbell corresponding to the endpoint of the first streaming endpoint, checking the endpoint list, and checking that the endpoint list has not recorded the third When a streaming endpoint is provided, a notification packet is provided to the first streaming endpoint, so that the first streaming state machine enters the total pipeline state and sends the first not-ready data packet. Such as the ultra-high-speed universal serial bus control method in request item 11, wherein: A plurality of endpoint operation doorbells directed at the first streaming endpoint carry a plurality of tag values, indicating a plurality of segment target transmissions of the first streaming endpoint; the first streaming state machine in the idle state is based on the first streaming endpoint. A ready data packet sent by the streaming endpoint corresponding to a target tag value switches to the ready transmission state, and then switches to the transmission state to complete a target transmission represented by the target tag value, resulting in the first streaming state The machine switches back to the idle state; and the ultra-high-speed universal serial bus control method further determines whether there is any connection with the first streaming endpoint when the first streaming endpoint completes the target transmission represented by the target tag value. The target transmission of the tag value is not completed. If it is completed, the first streaming endpoint is deleted from the endpoint list. For example, the ultra-high-speed Universal Serial Bus control method of request item 11 further includes: storing a task status note in the cache space, and providing the first stream endpoint with a first group of bits corresponding to a plurality of tag values, wherein: The metanormal state is a first state. When the corresponding tag value is configured to mark a segment of target transmission, it switches to a second state. It does not switch back to the first state until the segment of target transmission is completed; and the basis is the third state of the first state. A set of bits that determines the completion of all target transfers for the first streaming endpoint. For example, the ultra-high-speed universal serial bus control method of claim 11 further includes: operating a doorbell corresponding to a first endpoint of the first streaming endpoint, and checking that the endpoint The first streaming endpoint has not been recorded in the list, and a notification packet is provided to the first streaming endpoint, so that the first streaming state machine enters the total pipeline state, and the first not-ready data packet is sent out, so that the first streaming endpoint The point is recorded in the endpoint list, and the first streaming state machine is switched to the idle state; wherein, the first endpoint operating doorbell aimed at the first streaming endpoint carries a first tag value, indicating the first A first target transport for streaming endpoints. For example, the ultra-high-speed universal serial bus control method of claim 15 further includes: operating a doorbell corresponding to a second endpoint of the first streaming endpoint, and checking that the endpoint list records the first streaming endpoint, Skipping the switching of the first streaming state machine from the idle state to the total pipeline state; wherein, the second endpoint operation doorbell aligned with the first streaming endpoint carries a second tag value, indicating that the first streaming endpoint A second destination transport for the endpoint. For example, the ultra-high-speed universal serial bus control method of claim 16 further includes: following a ready data packet sent by the first streaming endpoint corresponding to the first tag value, causing the first streaming state machine to enter from the idle state. The preparation transmission state; sending another notification packet in response to the ready data packet of the first tag value, causing the first streaming state machine to switch from the preparation transmission state to the transmission state, causing the first streaming endpoint to A target transmission is completed; and after completing the first target transmission, the first streaming state machine is returned to the idle state, And it is determined that the second target transmission of the first streaming endpoint has not been realized, so that the endpoint list keeps recording the first streaming endpoint. For example, the ultra-high-speed universal serial bus control method of claim 17 further includes: following a ready data packet sent by the first streaming endpoint corresponding to the second tag value, causing the first streaming state machine to enter from the idle state. The preparation transmission state; sending another notification packet in response to the ready data packet of the second tag value, causing the first streaming state machine to switch from the preparation transmission state to the transmission state, causing the first streaming endpoint to The second target transmission is completed; and after completing the second target transmission, the first streaming state machine is returned to the idle state, and it is determined that the first streaming endpoint has no target transmission that has not been completed, and the first streaming endpoint is Removed from this endpoint list. For example, the ultra-high-speed universal serial bus control method of claim 16 further includes: when operating the doorbell on a third endpoint corresponding to a second streaming endpoint, it is checked that the endpoint list has not yet recorded the second streaming endpoint. The endpoint provides another notification packet to the second streaming endpoint, causing a second streaming state machine of the second streaming endpoint to enter the total pipeline state, and sends a second not ready data packet, causing the second streaming endpoint to enter the total pipeline state. The second streaming endpoint is recorded in the endpoint list, and the second streaming state machine is switched to the idle state as the second unready data packet is sent, waiting to enter the ready transmission state. For example, the ultra-high-speed universal serial bus control method of request 19, It further includes: when the endpoint list records the second streaming endpoint, skip switching the second streaming state machine from the idle state to the total pipeline state; and in all the second streaming endpoints After the target transmission is completed, the second streaming endpoint is deleted from the endpoint list.

Images