The present disclosure is related to the following commonly assigned co-pending U.S. patent application, which is incorporated herein by reference in its entirety for all purposes: application Ser. No. 11/779,714, filed concurrently with the present application, entitled “Segmented CRC Design In High Speed Networks.”
Embodiments of the present invention relate to data processing, and more particularly relate to techniques for efficient generation of Cyclical Redundancy Check (CRC) values in network devices.
A Cyclical Redundancy Check, or CRC, is a type of function that is used to detect errors in digital data. A typical n-bit CRC (e.g., CRC-16, CRC-32, etc.) receives as input a data block represented as a binary value, and divides the binary value by a predetermined n-bit binary divisor to generate a remainder that is characteristic of the data block. The remainder may be used as a checksum to determine, for example, if the data block is later altered during transmission or storage. In the art, the term CRC is often used to refer to both the function and its generated remainder; however, for clarity, the present disclosure will refer to the function as the CRC and the remainder as the CRC value.
In the field of data communications, network protocols such as Ethernet, ATM, and the like employ CRCs to detect transmission errors in messages (i.e., packets or frames) that are sent from one network device to another. For example, in a conventional Ethernet implementation, a transmitting network device (e.g., router, switch, host network interface, etc.) generates a CRC-32 value for each outgoing Ethernet frame, and appends the value to the frame prior to transmission. When the frame is received at a receiving network device, the CRC-32 value is stripped and a new CRC-32 value is generated for the frame. The new CRC-32 value is then compared to the received CRC-32 value to verify the integrity of the data contained within the frame.
A problem with conventional CRC processing circuit implementations is that they cannot efficiently support the high data throughput rates demanded by emerging wire transmission standards such as 100 G (i.e., 100 Gigabits per second (Gbps)) Ethernet. The data throughput of a CRC processing circuit is a function of its data line width and its clock speed. For example, a conventional parallel CRC circuit may process 64-bit wide data lines per clock cycle at a speed of 300 Megahertz (Mhz), thereby achieving a theoretical data throughput rate of approximately 64 bits*300 Mhz=19 Gbps, which is sufficient to support 10 G (i.e., 10 Gbps) Ethernet. However, achieving a data throughput rate of 100 Gbps and beyond is difficult for conventional CRC processing circuits.
There are several reasons why conventional CRC processing circuits cannot efficiently support high throughput rates such as 100 Gbps. 100 Gbps generally requires a 10 X or greater increase in either data line width or clock speed in a conventional 10 Gbps CRC processing circuit design, which is difficult to physically implement in hardware using currently available technologies. Implementing a large data line width also introduces timing issues at the gate level. Further, conventional parallel CRC designs require that the data lines of the input data stream be processed in order. Accordingly, in the case of Ethernet, an entire frame must be received by a receiving network device before a CRC value for the frame can be generated. This imposes a latency that makes it difficult to achieve theoretical data throughput rates, thereby further adversely affecting scalability.
Embodiments of the present invention provide techniques for efficient generation of CRC values in a network environment. Embodiments of the present invention include CRC processing components (e.g., circuits) that can generate CRC values at high data throughput rates (e.g., 100 Gbps or greater), while being capable of being implemented on currently available FPGAs. Accordingly, embodiments of the present invention may be used in network devices such as routers, switches, hubs, host network interfaces and the like to support high speed data transmission standards such as 100 G Ethernet and beyond.
In one set of embodiments, a network device receives a set of one or more data lines, where the data lines represent portions of a message. Each data line has a width, and at least one data line in the set of data lines is a residue line containing a portion of the message that is smaller in size than the width of the residue line. The portion of the message in the residue line is shifted from one boundary of the residue line to a second boundary of the residue line. A data line CRC value for each data line in the set of data lines is generated, and a message CRC value for the message is generated based on the data line CRC values. In this manner, a CRC value for a message such as an Ethernet frame may be efficiently generated by a network device.
In one set of embodiments, the message CRC value is generated by aggregating the data line CRC values using a logical operator. For example, the logical operator may be the exclusive-or (XOR) operator.
In various embodiments, generating the message CRC value comprises retrieving a first transformation matrix for one or more data lines in the set of data lines (excluding the residue line), multiplying the data line CRC value by its corresponding first transformation matrix, and generating a partial, accumulated message CRC value by aggregating the transformed CRC values for the data lines excluding the residue line. In one set of embodiments, the first transformation matrix may depend on the position of the data line relative to the other data lines in the set of data lines. Additionally, the first transformation matrix may be pre-computed and retrieved from memory. The embodiment further includes receiving a second transformation matrix, multiplying the partial, accumulated message CRC value by the second transformation matrix, and generating a final message CRC value based on the partial, accumulated message CRC value and the CRC value of the residue line. In one set of embodiments, the second transformation matrix may depend on the size of the message portion in the residue line. Additionally, the first and second transformation matrices may be pre-computed and retrieved from memory.
In one set of embodiments, the final message CRC value is generated by combining the transformed partial, accumulated message CRC value and the CRC value for the residue line using a logical operator. For example, the logical operator may be the XOR operator.
In further embodiments, a CRC value is generated for each data line by splitting each data line into a plurality of sublines, concurrently calculating a CRC value for each subline, and generating a data line CRC value for the data line based on the subline CRC values. Depending on the implementation, the sublines may be of equal or unequal sizes. In various embodiments, the step of generating a data line CRC value for the data line based on the subline CRC values may include retrieving a transformation matrix for each subline where the subline is not the last subline in the data line, multiplying the subline CRC value by its corresponding transformation matrix, and aggregating the transformed subline CRC values and the CRC value for the last subline to generate a data line CRC value. In one set of embodiments, the transformation matrix for a subline may depend on the position of the subline relative to the other sublines of the data line. Additionally, the transformation matrix for a subline may be pre-computed and retrieved from memory.
According to another embodiment of the present invention, a technique for generating a CRC value in a network device comprises receiving a set of one or more data lines, each data line in the set of data lines having a width and comprising a portion of a message, where at least one data line in the set of data lines is a residue line and where each data line in the set of data lines has a data granularity of X bits. The technique further includes calculating a CRC value for each data line in the set of data lines using a set of CRC generators, where each CRC generator is configured to take as input a value that is larger than X bits in size.
According to another embodiment of the present invention, a method for generating a CRC value in a network device comprises receiving a set of one or more data lines, each data line in the set of data lines having a width and comprising a portion of a message, where at least one data line in the set of data lines is a residue line. The method further comprises calculating a CRC value for each data line in the set of data lines using a set of CRC generators, where each CRC generator is configured to take as input a value that is the same size.
According to another embodiment of the present invention, a method for generating a CRC value in a network device comprises receiving a set of one or more data lines, each data line in the set of data lines having a width and comprising a portion of a message, and calculating a CRC value for each data line in the set of data lines using a set of CRC generators, the calculating being independent of the position of the data line relative to the other data lines in the set of data lines. In various embodiments, the calculating of a CRC value for each data line is performed concurrently. In further embodiments, at least one data line in the set of data lines is a residue line containing a portion of the message that is smaller than a width of the residue line.
According to another embodiment of the present invention, a technique for generating a CRC value in a network device includes receiving a set of one or more data lines, each data line in the set of data lines having a width of X bits and comprising a portion of a message, where at least one data line in the set of data lines is a residue line, and where each data line in the set of data lines has a data granularity of Y bits. The technique further includes calculating a CRC value for each data line in the set of data lines using a set of CRC generators, the number of CRC generators in the set of CRC generators being less than X divided by Y.
The foregoing, together with other features, embodiments, and advantages of the present invention, will become more apparent when referring to the following specification, claims, and accompanying drawings.
In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide an understanding of the present invention. It will be apparent, however, to one skilled in the art that the present invention may be practiced without some of these specific details. In other instances, well-known structures and devices are shown in block diagram form.
Embodiments of the present invention provide techniques for generating CRC values in an efficient manner. The CRC generation techniques described below may be applied to different domains and contexts. In one embodiment, the techniques may be used in the networking or data communication domain. In the networking environment, the CRC generation techniques may be employed by network devices such routers, switches, hubs, host network interfaces, etc. that use CRC-based error detection techniques to verify the integrity of data received by the devices. The CRC generation techniques of the present invention are scalable and can support high data throughput rates such as 100 Gbps and greater that are required by many high-speed data transmission standards.
Transmitting device 102 may transmit a data stream 104 to network device 110 using data link 106. Data link 106 may be any transmission medium(s), such as a wired (e.g., optical, twisted-pair copper, etc.) or wireless (e.g., 802.11, Bluetooth, etc.) link(s). Various different protocols may be used to communicate data stream 104 from transmitting device 102 to receiving network device 110. In one embodiment, data stream 104 comprises discrete messages (e.g., Ethernet frames, IP packets) that are transmitted using a network protocol (e.g., Ethernet, TCP/IP, etc.). An embodiment of data stream 104 is described in further detail with respect to
Network device 110 may receive data stream 104 at one or more ports 108. The data stream may comprise one or more messages received by network device 110. The data stream received over a port may then be routed to an interface 112, for example, a Media Access Controller (MAC) as found in Ethernet-based networking equipment. Interface 112 may be configured to perform various processing operations on the data stream, such as buffering of the data stream for forwarding to other components in the network device, updating header information in a message, determining a next destination for a received message, etc. Interface 112 may be implemented, for example, in one or more FPGAs and/or ASICs.
According to an embodiment of the present invention, interface 112 is configured to perform CRC-based error detection on data stream 104. To facilitate this, interface 112 may employ one or more CRC processing components 114. A CRC processing component is configured to generate a CRC value for data block input to the component. A CRC processing component may be implemented in hardware (e.g., microprocessor, logic device such as an FPGA or ASIC, etc.), in software, or combinations of hardware and software. In one embodiment, CRC processing component 114 is a logic-based circuit that is configured to generate a CRC value for a message received in data stream 104 by network device 110. In some embodiments, CRC processing component 114 may further include logic for verifying if the CRC value generated by the component for a received message matches a CRC value that is received from transmitting device 102 for the message. For example, as shown, transmitting device 102 may include a CRC generation component 116 configured to generate a CRC value for a message sent by transmitting device 102. The CRC value may then be appended to the message and extracted by network device 110 from the message in data stream 104. In this manner, CRC processing component 114 may be configured to generate a CRC value for the received data and use the generated value to verify the data integrity of the message received from the transmitting device.
In the example of
Network devices 152, 154, 156 and nodes 170, 178 may be any type of device capable of transmitting or receiving data via a communication channel, such as a router, switch, hub, host network interface, and the like. Sub-networks 168, 176 and network 164 may be any type of network that can support data communications using any of a variety of protocols, including without limitation Ethernet, ATM, token ring, FDDI, 802.11, TCP/IP, IPX, and the like. Merely by way of example, sub-networks 168, 176 and network 164 may be a LAN, a WAN, a virtual network (such as a virtual private network (VPN)), the Internet, an intranet, an extranet, a public switched telephone network (PSTN), an infra-red network, a wireless network, and/or any combination of these and/or other networks.
Data may be transmitted between any of network devices 152, 154, 156, sub-networks 168, 176, and nodes 170, 178 via one or more data links 158, 160, 162, 166, 174, 172, 180. Data links 158, 160, 162, 166, 174, 172, 180 maybe configured to support the same or different communication protocols. Further, data links 158, 160, 162, 166, 174, 172, 180 may support the same or different transmission standards (e.g., 10 G Ethernet for links between network devices 152, 154, 156 and network 164, 100 G Ethernet for links 172 between nodes 170 of sub-network 168).
In one embodiment, at least one data link 158, 160, 162, 166, 174, 172, 180 is configured to support 100 G Ethernet. Additionally, at least one device connected to that link (e.g., a receiving device) is configured to support a data throughput of at least 100 Gbps. In this embodiment, the receiving device may correspond to receiving device 110 of
As indicated above, data stream 104 may comprise data corresponding to one or more messages that are received by receiving network device 110. In the case of the Ethernet protocol, a message corresponds to an Ethernet frame. Messages received via data stream 104 may be of the same size or of variable size. For example, Ethernet supports message sizes up to 1.4 kilobytes. In one embodiment, data stream 104 is received by interface 112, which may be a MAC, and then presented to CRC processing component 114 for generation of a CRC value for a message. In one embodiment, the data stream is presented to CRC processing component 114 in the form of data lines.
The width (i.e., size) of a data line may vary from one embodiment to another. The width of the data line is independent of the size of a message supported by a particular transmission protocol. The width of a data line corresponds to the maximum size of data that can be provided as input to CRC processing component 114 per unit of time (e.g., per clock cycle). In the embodiment depicted in
A message may be contained in one data line or may be spread over multiple data lines with each data line containing a portion of the message. If the size of a message is larger that the data line width, the message will be spread over multiple data lines that may be received and processed over a number of clock cycles. In
In certain instances, a data line for a message may contain message data that is smaller in size that the width of the data line. This may occur, for instance, if the total size of the message is smaller than the data line width or is not a multiple of the data line width (i.e., the message has a data granularity that is not aligned with the data line width). As used herein, data granularity refers to the smallest physical unit of data that is transmitted using a particular transmission protocol. In the case of Ethernet protocol, the data granularity is generally 8 bits. Thus, an Ethernet frame may vary in size from 8 bits to 1.4 kilobytes (the maximum frame size) in 8 bit increments (the data granularity). Returning to
According to an embodiment of the present invention, the data lines corresponding to a message are provided to CRC processing component 114 for generating a CRC value for the message.
At step 302, a set of one or more data lines is received, where each data line in the set comprises a portion of a message. Generally, the width of each data line is fixed, and is determined by the data line width supported by the CRC processing component. Thus, if method 300 is performed by a CRC processing component that supports a data line width of 64 bits, the width of each received data line will be 64 bits. Similarly, if method 300 is performed by a CRC processing component that supports a data line width of 640 bits, the width of each received data line will be 640 bits.
If there is a residue line in the set of data lines, the portion of the message in the residue line is shifted from a first boundary of the residue line to a second boundary of the residue line (step 304). In an embodiment, shifting is a bitwise shift operation, where one or more bits in the residue line are moved one or more bit positions and the vacated bit positions are filled in with zeroes. For example, assume that the residue line has a width of 8 bits and contains the binary value 11010000, where the message data is 1101, and where the most significant bit (MSB) boundary is on the left side and the least significant bit boundary (LSB) is on the right side. The data in the residue line may be shifted from the MSB boundary to the LSB boundary such that the binary value in the residue line becomes 00001101. Alternatively, the data in the residue line may be shifted from the LSB boundary to the MSB boundary.
Performing the above shift facilitates computation of a CRC value for the residue line. In the above example, the CRC value for 1101 (i.e., the message data included in the residue line) cannot be directly computed using bit string 11010000 as an input to a CRC generator because the trailing four zeros alter the CRC calculation resulting in a different (incorrect) CRC value being generated. However, if 11010000 is shifted to produce 00001101, the correct CRC value for 1101 can be directly computed using bit string 00001101 because the leading fours zeros do not affect the CRC computation.
In one embodiment, the shifting in step 304 may be performed using a conventional barrel shifter. In other embodiments, other hardware and/or software-based methods known to those skilled in the art may be used for shifting.
At step 306, a CRC value (referred to as a data line CRC value) for each data line in the set of data lines corresponding to the message is independently generated. In other words, the calculation of a CRC value for one data line is not dependent on the CRC value for any other data line in the set of data lines for the message. In one embodiment, CRC processing component 114 is configured to generate one data line CRC value per a unit of time (e.g., clock cycle) for the data line received in the unit of time.
Different techniques may be used for calculating a data line CRC value for a data line. In one embodiment, each data line is segmented into sublines, and CRC values are generated for each subline. Each subline may be processed by a separate CRC generator to generate a CRC for the subline. The CRC value for the data line is then calculated based upon the CRC values calculated for the sublines. In alternative embodiments, each data line may be processed as a whole (e.g., passed to a single CRC generator) to generate a data line CRC value.
Once CRC values for each data line including the residue line are generated, a message CRC value for the message is generated based upon the data line CRC values (step 308). In one embodiment, the CRC for the message is calculated by aggregating the CRC values calculated for the data lines using a logical operator such as the exclusive-or (XOR) operator. In another embodiment, one or more of the CRC values generated for the data lines (excluding the residue data line) may be transformed using a transformation matrix and the transformed values may be aggregated using a logical operator, such as the exclusive-or (XOR) operator, to generated a partial, accumulated message CRC value. The partial, accumulated message CRC value may then be transformed using a residue transformation matrix and aggregated with the CRC value of the residue line to generate a message CRC value. This embodiment is discussed in further detail with respect to
In some embodiments, the message CRC value generated in 308 may optionally be used to verify the integrity of the message (step 310). This may be done by comparing the CRC generated in 308 with a previously calculated message CRC value. The previously calculated message CRC may be communicated from the transmitting device and may be appended to the message received by the receiving network device. The receiving network device is able to extract this previously calculated CRC value and compare it to the message CRC value generated in 308 in order to determine the integrity of the message. In one embodiment, integrity of the message is confirmed if the message CRC value generated in 308 matches the previously calculated CRC value.
It should be appreciated that the specific steps illustrated in
As indicated above, different techniques may be used to calculate a data line CRC value for a data line. In one embodiment, the data line is subdivided into sublines and CRC values calculated for the sublines. The CRC value for the data line is then calculated based upon the subline CRC values.
At step 502, a data line containing data for a message is received (i.e., the current data line LC of the message). At step 504, the data line is segmented into N sublines SLC1, SLC2, . . . SCCN. The sizes of the sublines may be the same or may be different. For example, as shown in
At step 506, a CRC value is calculated for each subline generated in 504. In one embodiment, the CRC values for the sublines are calculated concurrently (for example, using N CRC generators).
At step 508, a data line CRC value for the current data line LC is generated based upon the subline CRC values calculated in step 506. Various other techniques may be used for generating a CRC value for the data line based upon CRC values calculated for the sublines.
The processing in step 508 may include multiple sub-steps as shown in
The CRC value generated for each subline in 506 (excluding the last subline SLCN) is then transformed by multiplying the CRC value with the transformation matrix retrieved for the subline in 552 (step 554). The multiplication yields a transformed CRC value for each subline (except the last subline). Step 554 is performed to mathematically adjust each subline CRC value (excluding the subline value of for the last subline SLCN) based on the offset of the subline in data line LC. This allows each subline CRC value to be generated independently of each other and then adjusted based upon the position of the subline.
The transformation matrices for the sublines may be pre-calculated and stored in memory from where they can be accessed during processing. The transformation matrix for each subline CRC is based on the position of the subline relative to the other sublines of LC. Since the last subline SLCN has no offset, the CRC value for SLCN does not need to be adjusted and hence there is no need to retrieve a transformation matrix for the last subline.
The transformed CRC values and the CRC value for the last subline are then aggregated to generate a CRC for the data line (step 556). Various different techniques may be used for aggregating the sublines. In one embodiment, the aggregation is performed using a logical operator such as the exclusive-or (XOR) operator.
It should be appreciated that the specific steps illustrated in
As shown, circuit 600 receives as input a data line 602 having a width of 640 bits, and routes data line 602 to a residue line shift unit 604. If data line 602 is a residue line, the contents of data line 602 are shifted from one boundary to another as previously described with respect to step 304 of
Data line 602 is then segmented into five 128-bit sublines (606, 608, 610, 612, 614). The sublines are concurrently passed into five 128-bit-in CRC generators 616, 618, 620, 622, 624, and the CRC generators output a fixed-size CRC value for each subline (e.g., 32 bits for CRC-32).
As shown, the generated CRC values for the first four sublines 606, 608, 610, 612 are routed to subline CRC transform units 626, 628, 630, 632 to be transformed. In this embodiment, the first four sublines are the four sublines that are most closely aligned to the MSB boundary of data line 602. Each CRC transform unit is configured to retrieve a transformation matrix for the subline whose CRC value is input to the CRC transform unit and multiply the subline CRC value by the retrieved matrix. In one embodiment, the transformation matrices are retrieved from a transformation matrix lookup table 634. Table 634 may be implemented in memory (such as an EEPROM, Flash ROM, etc.), and may consist of one or more physical or logical memory units.
Once the CRC values for sublines 606, 608, 610, 612 have been adjusted or transformed via transform units 526, 528, 530, 532, the output from those transform units represent the transformed CRC values for the sublines. As described above, the CRC value for the last subline 614 does not need to be adjusted.
The transformed CRC values for the sublines and the non-transformed CRC value for the last subline are then aggregated using an XOR unit 636. The output 638 from XOR unit 636 corresponds to the generated CRC value for data line 602. In one embodiment, circuit 600 is configured to generate data line CRC value 638 from input data line 602 in a single clock cycle.
It should be appreciated that diagram 600 illustrates one exemplary circuit for generating a data line CRC value, and other alternative configurations are contemplated. For example, although input data line 602 is shown as having a width of 640 bits, circuit 600 may be configured to take as input a data line of any other width. Additionally, although five 128-bit-in generators are shown, circuit 600 may be configured to incorporate any other number and types of CRC generators, such as ten 64 bit-in CRC generators. One of ordinary skill in the art would recognize many variations, modifications, and alternatives.
At step 702, the CRC values for one or more data lines in the set of data lines (excluding the residue line) are multiplied by corresponding transformation matrices to generate transformed CRC values for the one or more data lines. This step is used to mathematically adjust the CRC value for each of the one or more data lines based on the position of the data line in the message. This allows each data line CRC value to be calculated independently of each other and then transformed using the transformation matrices. In various embodiments, the transformation matrix for each data line is pre-computed and is dependent on the position of the data line relative to other data lines of message. These pre-computed matrices may be stored and retrieved from one or more tables in memory.
A partial, accumulated message CRC value is then generated based on the CRC values for all of the data lines in the set of data lines excluding the residue line (step 704). In one embodiment, the partial, accumulated message CRC value is generated by aggregating the transformed CRC values for one or more data lines (excluding the residue line) with the non-transformed CRC values for one or more data lines (excluding the residue line). For example, for message 202 of
At steps 706 and 708, a residue transformation matrix is retrieved from memory and the partial, accumulated message CRC value generated in 704 is multiplied by the residue transformation matrix. In various embodiments, the residue transformation matrix is used to mathematically adjust the partial, accumulated message CRC value based on the offset of the second-to-last data line (i.e., the data line before the residue line) from the end of the message. Assuming a message spread over M data lines, this step allows the first M-1 data lines to be computed independently of the residue (i.e., Mth) data line. In various embodiments, the residue transformation matrix is pre-computed and is dependent on the size of the message portion in the residue line. In some embodiments, the residue transformation matrix is retrieved from the same table(s) as the data line transformation matrices of step 702. In alternative embodiments, the residue transformation matrix is stored in a separate table in memory.
A final message CRC value is then generated by aggregating the result of 708 with the CRC value of the residue line (step 710). This aggregation may be performed using a logical operator such as the XOR operator.
It should be appreciated that the specific steps illustrated in
If the current line LC is not a residue line of the message, the CRC value 802 for LC is routed to line CRC transform unit 814. Based on current line count C and total line count 808, an appropriate transformation matrix for LC is retrieved from transformation matrix lookup table 816 and the matrix is multiplied with the CRC value to generate a transformed CRC value for the data line. In one embodiment, a transformation matrix is not retrieved for the second-to-last data line of the message. The output of line CRC transform unit 814 is then passed to XOR unit 818, which stores a partial, accumulated CRC value for the message. If C=1, then the output of line CRC transform unit 814 is simply stored in XOR unit 818. If C>1, then the output of line CRC transform unit 814 is XOR'ed with the partial, accumulated message CRC value already stored in unit 818 to generate a new partial, accumulated message CRC value, and this new value is stored in unit 818.
The above process is repeated over successive clock cycles for successive data lines of the message until a residue line is reached (i.e., current line count C=total line count 808). Once the current line becomes a residue line, the CRC value for the residue line 802 is passed to a delay unit 824. Concurrently, pad value 804 is passed to line CRC transform unit 814, multiplied with an appropriate transformation matrix from table 816, and aggregated with the partial, accumulated message CRC value in XOR unit 818. The partial, accumulated message CRC value is then routed to an accumulated message CRC transform unit 820. Unit 820 retrieves a residue transformation matrix from a second transformation matrix lookup table 822, and multiplies the residue transformation matrix with the partial, accumulated message CRC value. In an exemplary embodiment, the residue transformation matrix is based on the size of the message portion in the residue line.
Finally, the output of unit 820 is aggregated (e.g., XOR'ed) with residue line CRC value 802 at XOR unit 728, and a final message CRC value 828 is generated.
In various embodiments, circuit 800 may be configured to interoperate with circuit 600 of
It should be appreciated that circuit 800 illustrates one example of a circuit for generating a message CRC value, and other alternative configurations are contemplated. For example, although circuit 800 aggregates data line CRC values incrementally (via partial, accumulated message CRC value), circuit 800 may be configured to postpone the aggregation of the data line CRC values until the last data line of the message has been received. Additionally, although circuit 800 is shown as receiving a pad value 804, other embodiments may not require a pad value. One of ordinary skill in the art would recognize many variations, modifications, and alternatives.
To further clarify the operation of circuit 800, the following table shows examples of values for (1) received LC CRC value 802, (2) the partial, accumulated message CRC value stored in unit 818, and (3) final message CRC value 828 as circuit 800 processes message 202 of
At time T1, the CRC value for data line L1 (L1CRC) is received. Since L1 is offset from the beginning of residue line L4 by two full data lines, L1CRC is multiplied by a corresponding transformation matrix T2L, and the product of this multiplication is stored as the partial, accumulated message CRC value.
At time T2, the CRC value for data line L2 (L2CRC) is received. Since L2 is offset from the beginning of residue line L4 by one full data line, L2CRC is multiplied by a corresponding transformation matrix T1L. The product of this multiplication is then XOR'ed (denoted by the symbol ⊕) with the partial, accumulated message CRC value to generate a new partial value L1CRC*T2L⊕L2CRC*T1L.
At time T3, the CRC value for data line L3 (L3CRC) is received. Since L3 is the second-to-last data line in message 202, L3 has no offset from the beginning of residue line L4. Accordingly, L3CRC is not multiplied by any transformation matrix. Rather, L3CRC is simply XOR'ed with the partial, accumulated message CRC value to generate a new partial value L1CRC*T2L⊕L2CRC*T1L⊕L3CRC.
At time T4, the CRC value for residue line L4 (L4CRC) is received. Since L4 is the final data line in message 202, a pad value (32h′FFFF_FFFF for Ethernet) is multiplied by a corresponding transformation matrix T3L and XOR'ed with the partial, accumulated message CRC value to generate a new partial value L1CRC*T2L⊕L2CRC*T1L⊕L3CRC⊕32′hFFFF_FFFF*T3L. The new partial, accumulated message CRC value is then multiplied by a residue transformation matrix TRes. Finally, the product of that multiplication is XOR'ed with the residue line CRC value L4CRC to generate the message CRC value for message 202.
Since, in various embodiments, circuit 900 does not require as input the total number of data lines for a message, circuit 900 can begin processing the message before all of the data lines of the message have been received. In one set of embodiments, circuit 900 may be implemented by modifying the transformation matrices used by circuit 800. For example, the modified matrices used by circuit 900 may be based on the offset of a data line from the maximum size of a message, rather than the offset of the data line from the residue line. Further, circuit 900 may employ an additional inverse transformation matrix (stored in transformation matrix lookup table 904). The inverse matrix may be used to transform the partial, accumulated message CRC value prior to being multiplied by the residue transformation matrix.
Embodiments of the present invention provide solutions for generating CRC values. Since the residue line of a message is handled by shifting the contents of the line (rather than by incorporating multiple CRC generators to account for each possible size of the message data in the residue line as done in the prior art), embodiments of the present invention may be implemented with a number of CRC generators that is independent of data line width, thus improving scalability. For example, circuit 600 of
Additionally, shifting the contents of the residue line allows embodiments of the present invention to be implemented with one or more CRC generators where (1) the input for each CRC generator is larger than the data granularity of an input message, (2) the input for each CRC generator is smaller than the data line width of a CRC processing circuit; and/or (3) the input for each CRC generator is the same size. For example, circuit 600 of
Further, since the CRC values for the data lines (and sub lines) of a message are mathematically adjusted by an appropriate transformation matrix prior to being aggregated, the data lines can be processed out of order. In the case of Ethernet, this allows a CRC processing component to begin processing a frame before the entire frame has been received over the wire, thereby further increasing performance and scalability.
Although specific embodiments of the invention have been described, various modifications, alterations, alternative constructions, and equivalents are also encompassed within the scope of the invention. The described invention is not restricted to operation within certain specific data processing environments, but is free to operate within a plurality of data processing environments. Additionally, although the present invention has been described using a particular series of transactions and steps, it should be apparent to those skilled in the art that the scope of the present invention is not limited to the described series of transactions and steps.
Further, while the present invention has been described using a particular combination of hardware and software, it should be recognized that other combinations of hardware and software are also within the scope of the present invention. The present invention may be implemented only in hardware, or only in software, or using combinations thereof.
The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. It will, however, be evident that additions, subtractions, deletions, and other modifications and changes may be made thereunto without departing from the broader spirit and scope of the invention as set forth in the claims.
Number | Name | Date | Kind |
---|---|---|---|
3866175 | Seifert, Jr. et al. | Feb 1975 | A |
4325119 | Grandmaison et al. | Apr 1982 | A |
4348725 | Farrell et al. | Sep 1982 | A |
4628480 | Floyd | Dec 1986 | A |
4667323 | Engdahl et al. | May 1987 | A |
4683564 | Young et al. | Jul 1987 | A |
4698748 | Juzswik et al. | Oct 1987 | A |
4723243 | Joshi et al. | Feb 1988 | A |
4754482 | Weiss | Jun 1988 | A |
4791629 | Burns et al. | Dec 1988 | A |
4794629 | Pastyr et al. | Dec 1988 | A |
4807280 | Posner et al. | Feb 1989 | A |
4876681 | Hagiwara et al. | Oct 1989 | A |
4896277 | Vercellotti et al. | Jan 1990 | A |
4985889 | Frankish et al. | Jan 1991 | A |
5101404 | Kunimoto et al. | Mar 1992 | A |
5136584 | Hedlund | Aug 1992 | A |
5195181 | Bryant et al. | Mar 1993 | A |
5208856 | Leduc et al. | May 1993 | A |
5224108 | McDysan et al. | Jun 1993 | A |
5231633 | Hluchyj et al. | Jul 1993 | A |
5280582 | Yang et al. | Jan 1994 | A |
5282196 | Clebowicz | Jan 1994 | A |
5287477 | Johnson et al. | Feb 1994 | A |
5299190 | LaMaire et al. | Mar 1994 | A |
5299195 | Shah | Mar 1994 | A |
5301192 | Henrion | Apr 1994 | A |
5307345 | Lozowick et al. | Apr 1994 | A |
5323386 | Wiher et al. | Jun 1994 | A |
5365512 | Combs et al. | Nov 1994 | A |
5377189 | Clark | Dec 1994 | A |
5390173 | Spinney et al. | Feb 1995 | A |
5392279 | Taniguchi | Feb 1995 | A |
5406643 | Burke et al. | Apr 1995 | A |
5408469 | Opher et al. | Apr 1995 | A |
5430442 | Kaiser et al. | Jul 1995 | A |
5436893 | Barnett | Jul 1995 | A |
5461615 | Henrion | Oct 1995 | A |
5490258 | Fenner | Feb 1996 | A |
5506840 | Pauwels et al. | Apr 1996 | A |
5506841 | Sandquist | Apr 1996 | A |
5521923 | Willmann et al. | May 1996 | A |
5546385 | Caspi et al. | Aug 1996 | A |
5550816 | Hardwick et al. | Aug 1996 | A |
5563948 | Diehl et al. | Oct 1996 | A |
5566170 | Bakke et al. | Oct 1996 | A |
5598410 | Stone | Jan 1997 | A |
5600795 | Du | Feb 1997 | A |
5619497 | Gallagher et al. | Apr 1997 | A |
5640504 | Johnson et al. | Jun 1997 | A |
5646878 | Samra | Jul 1997 | A |
5663952 | Gentry, Jr. | Sep 1997 | A |
5663959 | Nakagawa et al. | Sep 1997 | A |
5666353 | Klausmeier et al. | Sep 1997 | A |
5721819 | Galles et al. | Feb 1998 | A |
5732080 | Ferguson et al. | Mar 1998 | A |
5734826 | Olnowich et al. | Mar 1998 | A |
5740176 | Gupta et al. | Apr 1998 | A |
5745708 | Weppler et al. | Apr 1998 | A |
5751710 | Crowther et al. | May 1998 | A |
5802287 | Rostoker et al. | Sep 1998 | A |
5815146 | Youden et al. | Sep 1998 | A |
5818816 | Chikazawa et al. | Oct 1998 | A |
5835496 | Yeung et al. | Nov 1998 | A |
5838684 | Wicki et al. | Nov 1998 | A |
5862350 | Coulson | Jan 1999 | A |
5864555 | Mathur et al. | Jan 1999 | A |
5867675 | Lomelino et al. | Feb 1999 | A |
5870538 | Manning et al. | Feb 1999 | A |
5872769 | Caldara et al. | Feb 1999 | A |
5872783 | Chin | Feb 1999 | A |
5875200 | Glover et al. | Feb 1999 | A |
5896380 | Brown et al. | Apr 1999 | A |
5907566 | Benson et al. | May 1999 | A |
5907660 | Inoue et al. | May 1999 | A |
5909686 | Muller et al. | Jun 1999 | A |
5915094 | Kouloheris et al. | Jun 1999 | A |
5920566 | Hendel et al. | Jul 1999 | A |
5920886 | Feldmeier | Jul 1999 | A |
5936939 | Des Jardins et al. | Aug 1999 | A |
5936966 | Ogawa et al. | Aug 1999 | A |
5956347 | Slater | Sep 1999 | A |
5999528 | Chow et al. | Dec 1999 | A |
6000016 | Curtis et al. | Dec 1999 | A |
6016310 | Muller et al. | Jan 2000 | A |
6023471 | Haddock et al. | Feb 2000 | A |
6031843 | Swanbery et al. | Feb 2000 | A |
6035414 | Okazawa et al. | Mar 2000 | A |
6038288 | Thomas et al. | Mar 2000 | A |
6067298 | Shinohara | May 2000 | A |
6067606 | Holscher et al. | May 2000 | A |
6076115 | Sambamurthy et al. | Jun 2000 | A |
6081522 | Hendel et al. | Jun 2000 | A |
6088356 | Hendel et al. | Jul 2000 | A |
6094434 | Kotzur et al. | Jul 2000 | A |
6104696 | Kadambi et al. | Aug 2000 | A |
6104700 | Haddock et al. | Aug 2000 | A |
6108306 | Kalkunte et al. | Aug 2000 | A |
6118787 | Kalkunte et al. | Sep 2000 | A |
6125417 | Bailis et al. | Sep 2000 | A |
6128666 | Muller et al. | Oct 2000 | A |
6144668 | Bass et al. | Nov 2000 | A |
6147996 | Laor et al. | Nov 2000 | A |
6151301 | Holden | Nov 2000 | A |
6151497 | Yee et al. | Nov 2000 | A |
6154446 | Kadambi et al. | Nov 2000 | A |
6157643 | Ma | Dec 2000 | A |
6160809 | Adiletta et al. | Dec 2000 | A |
6160812 | Bauman et al. | Dec 2000 | A |
6172990 | Deb et al. | Jan 2001 | B1 |
6178520 | DeKoning et al. | Jan 2001 | B1 |
6181699 | Crinion et al. | Jan 2001 | B1 |
6185222 | Hughes | Feb 2001 | B1 |
6195335 | Calvignac et al. | Feb 2001 | B1 |
6201492 | Amar et al. | Mar 2001 | B1 |
6222845 | Shue et al. | Apr 2001 | B1 |
6243667 | Kerr et al. | Jun 2001 | B1 |
6249528 | Kothary | Jun 2001 | B1 |
6263374 | Olnowich et al. | Jul 2001 | B1 |
6272144 | Berenbaum et al. | Aug 2001 | B1 |
6304903 | Ward | Oct 2001 | B1 |
6320859 | Momirov | Nov 2001 | B1 |
6333929 | Drottar et al. | Dec 2001 | B1 |
6335932 | Kadambi et al. | Jan 2002 | B2 |
6335935 | Kadambi et al. | Jan 2002 | B2 |
6343072 | Bechtolsheim et al. | Jan 2002 | B1 |
6351143 | Guccione et al. | Feb 2002 | B1 |
6356550 | Williams | Mar 2002 | B1 |
6356942 | Bengtsson et al. | Mar 2002 | B1 |
6363077 | Wong et al. | Mar 2002 | B1 |
6366557 | Hunter | Apr 2002 | B1 |
6369855 | Chauvel et al. | Apr 2002 | B1 |
6421352 | Manaka et al. | Jul 2002 | B1 |
6424658 | Mathur | Jul 2002 | B1 |
6424659 | Viswanadham et al. | Jul 2002 | B2 |
6427185 | Ryals et al. | Jul 2002 | B1 |
6430190 | Essbaum et al. | Aug 2002 | B1 |
6457175 | Lerche | Sep 2002 | B1 |
6459705 | Cheng | Oct 2002 | B1 |
6460088 | Merchant | Oct 2002 | B1 |
6463063 | Bianchini, Jr. et al. | Oct 2002 | B1 |
6466608 | Hong et al. | Oct 2002 | B1 |
6470436 | Croft et al. | Oct 2002 | B1 |
6473428 | Nichols et al. | Oct 2002 | B1 |
6473433 | Bianchini, Jr. et al. | Oct 2002 | B1 |
6477174 | Dooley et al. | Nov 2002 | B1 |
6480477 | Treadaway et al. | Nov 2002 | B1 |
6490280 | Leung | Dec 2002 | B1 |
6493347 | Sindhu et al. | Dec 2002 | B2 |
6496502 | Fite et al. | Dec 2002 | B1 |
6505281 | Sherry | Jan 2003 | B1 |
6510138 | Pannell | Jan 2003 | B1 |
6522656 | Gridley | Feb 2003 | B1 |
6532229 | Johnson et al. | Mar 2003 | B1 |
6532234 | Yoshikawa | Mar 2003 | B1 |
6535504 | Johnson et al. | Mar 2003 | B1 |
6549519 | Michels et al. | Apr 2003 | B1 |
6553370 | Andreev et al. | Apr 2003 | B1 |
6556208 | Congdon et al. | Apr 2003 | B1 |
6567404 | Wilford | May 2003 | B1 |
6577631 | Keenan et al. | Jun 2003 | B1 |
6587432 | Putzolu et al. | Jul 2003 | B1 |
6591302 | Boucher et al. | Jul 2003 | B2 |
6601186 | Fox et al. | Jul 2003 | B1 |
6606300 | Blanc et al. | Aug 2003 | B1 |
6628650 | Saite et al. | Sep 2003 | B1 |
6633580 | Torudbakken et al. | Oct 2003 | B1 |
6636483 | Pannell | Oct 2003 | B1 |
6643269 | Fan et al. | Nov 2003 | B1 |
6654342 | Dittia et al. | Nov 2003 | B1 |
6654346 | Mahalingaiah et al. | Nov 2003 | B1 |
6654370 | Quirke et al. | Nov 2003 | B1 |
6654373 | Maher, III et al. | Nov 2003 | B1 |
6658002 | Ross et al. | Dec 2003 | B1 |
6661791 | Brown | Dec 2003 | B1 |
6671275 | Wong et al. | Dec 2003 | B1 |
6678248 | Haddock et al. | Jan 2004 | B1 |
6681332 | Byrne et al. | Jan 2004 | B1 |
6683872 | Saito | Jan 2004 | B1 |
6687217 | Chow et al. | Feb 2004 | B1 |
6687247 | Wilford et al. | Feb 2004 | B1 |
6691202 | Vasquez et al. | Feb 2004 | B2 |
6696917 | Heitner et al. | Feb 2004 | B1 |
6697359 | George | Feb 2004 | B1 |
6697368 | Chang et al. | Feb 2004 | B2 |
6700894 | Shung | Mar 2004 | B1 |
6708000 | Nishi et al. | Mar 2004 | B1 |
6721229 | Cole | Apr 2004 | B1 |
6721268 | Ohira et al. | Apr 2004 | B1 |
6721313 | Van Duyne | Apr 2004 | B1 |
6721338 | Sato | Apr 2004 | B1 |
6731875 | Kartalopoulos | May 2004 | B1 |
6735218 | Chang et al. | May 2004 | B2 |
6745277 | Lee et al. | Jun 2004 | B1 |
6747971 | Hughes et al. | Jun 2004 | B1 |
6751224 | Parruck et al. | Jun 2004 | B1 |
6754881 | Kuhlmann et al. | Jun 2004 | B2 |
6765866 | Wyatt | Jul 2004 | B1 |
6775706 | Fukumoto et al. | Aug 2004 | B1 |
6778546 | Epps et al. | Aug 2004 | B1 |
6781990 | Puri et al. | Aug 2004 | B1 |
6785290 | Fujisawa et al. | Aug 2004 | B1 |
6788697 | Aweya et al. | Sep 2004 | B1 |
6792484 | Hook | Sep 2004 | B1 |
6792502 | Pandya et al. | Sep 2004 | B1 |
6798740 | Senevirathne et al. | Sep 2004 | B1 |
6804220 | Odenwalder et al. | Oct 2004 | B2 |
6804731 | Chang et al. | Oct 2004 | B1 |
6807179 | Kanuri et al. | Oct 2004 | B1 |
6807363 | Abiko et al. | Oct 2004 | B1 |
6810038 | Isoyama et al. | Oct 2004 | B1 |
6810046 | Abbas et al. | Oct 2004 | B2 |
6813243 | Epps et al. | Nov 2004 | B1 |
6813266 | Chiang et al. | Nov 2004 | B1 |
6816467 | Muller et al. | Nov 2004 | B1 |
6831923 | Laor et al. | Dec 2004 | B1 |
6831932 | Boyle et al. | Dec 2004 | B1 |
6836808 | Bunce et al. | Dec 2004 | B2 |
6839346 | Kametani | Jan 2005 | B1 |
6842422 | Bianchini, Jr. | Jan 2005 | B1 |
6854117 | Roberts | Feb 2005 | B1 |
6856600 | Russell et al. | Feb 2005 | B1 |
6859438 | Haddock et al. | Feb 2005 | B2 |
6865153 | Hill et al. | Mar 2005 | B1 |
6901072 | Wong | May 2005 | B1 |
6906936 | James et al. | Jun 2005 | B1 |
6912637 | Herbst | Jun 2005 | B1 |
6920154 | Aschler | Jul 2005 | B1 |
6925516 | Struhsaker et al. | Aug 2005 | B2 |
6934305 | Duschatko et al. | Aug 2005 | B1 |
6937606 | Basso et al. | Aug 2005 | B2 |
6946948 | McCormack et al. | Sep 2005 | B2 |
6957258 | Maher, III et al. | Oct 2005 | B2 |
6959007 | Vogel et al. | Oct 2005 | B1 |
6973092 | Zhou et al. | Dec 2005 | B1 |
6975599 | Johnson et al. | Dec 2005 | B1 |
6978309 | Dorbolo | Dec 2005 | B1 |
6980552 | Belz et al. | Dec 2005 | B1 |
6982974 | Saleh et al. | Jan 2006 | B1 |
6990102 | Kaniz et al. | Jan 2006 | B1 |
6993032 | Dammann et al. | Jan 2006 | B1 |
6996663 | Marsteiner | Feb 2006 | B1 |
7005812 | Mitchell | Feb 2006 | B2 |
7009968 | Ambe et al. | Mar 2006 | B2 |
7012919 | So et al. | Mar 2006 | B1 |
7050430 | Kalkunte et al. | May 2006 | B2 |
7080238 | Van Hoof et al. | Jul 2006 | B2 |
7082133 | Lor et al. | Jul 2006 | B1 |
7103041 | Speiser et al. | Sep 2006 | B1 |
7120744 | Klein | Oct 2006 | B2 |
7126948 | Gooch et al. | Oct 2006 | B2 |
7126956 | Scholten | Oct 2006 | B2 |
7151797 | Limberg | Dec 2006 | B2 |
7161948 | Sampath et al. | Jan 2007 | B2 |
7167471 | Calvignac et al. | Jan 2007 | B2 |
7176911 | Kidono et al. | Feb 2007 | B1 |
7185141 | James et al. | Feb 2007 | B1 |
7185266 | Blightman et al. | Feb 2007 | B2 |
7187687 | Davis et al. | Mar 2007 | B1 |
7190696 | Manur et al. | Mar 2007 | B1 |
7191277 | Broyles | Mar 2007 | B2 |
7191468 | Hanner | Mar 2007 | B2 |
7203194 | Chang et al. | Apr 2007 | B2 |
7206283 | Chang et al. | Apr 2007 | B2 |
7212536 | Mackiewich et al. | May 2007 | B2 |
7218637 | Best et al. | May 2007 | B1 |
7219293 | Tsai et al. | May 2007 | B2 |
7228509 | Dada et al. | Jun 2007 | B1 |
7236490 | Chang et al. | Jun 2007 | B2 |
7237058 | Srinivasan | Jun 2007 | B2 |
7249306 | Chen | Jul 2007 | B2 |
7266117 | Davis | Sep 2007 | B1 |
7277425 | Sikdar | Oct 2007 | B1 |
7283547 | Hook et al. | Oct 2007 | B1 |
7286534 | Kloth | Oct 2007 | B2 |
7324509 | Ni | Jan 2008 | B2 |
7355970 | Lor | Apr 2008 | B2 |
7356030 | Chang et al. | Apr 2008 | B2 |
7366100 | Anderson et al. | Apr 2008 | B2 |
7391769 | Rajkumar et al. | Jun 2008 | B2 |
7428693 | Obuchi et al. | Sep 2008 | B2 |
7468975 | Davis | Dec 2008 | B1 |
7512127 | Chang et al. | Mar 2009 | B2 |
7558193 | Bradbury et al. | Jul 2009 | B2 |
7561590 | Walsh | Jul 2009 | B1 |
7596139 | Patel et al. | Sep 2009 | B2 |
7609617 | Appanna et al. | Oct 2009 | B2 |
7613991 | Bain | Nov 2009 | B1 |
7636369 | Wong | Dec 2009 | B2 |
7649885 | Davis et al. | Jan 2010 | B1 |
7657703 | Singh | Feb 2010 | B1 |
7738450 | Davis | Jun 2010 | B1 |
7813367 | Wong | Oct 2010 | B2 |
7817659 | Wong | Oct 2010 | B2 |
7830884 | Davis | Nov 2010 | B2 |
7903654 | Bansal | Mar 2011 | B2 |
7953922 | Singh | May 2011 | B2 |
7953923 | Singh | May 2011 | B2 |
20010001879 | Kubik et al. | May 2001 | A1 |
20010007560 | Masuda et al. | Jul 2001 | A1 |
20010026551 | Horlin | Oct 2001 | A1 |
20010048785 | Steinberg | Dec 2001 | A1 |
20010053150 | Clear et al. | Dec 2001 | A1 |
20020001307 | Nguyen et al. | Jan 2002 | A1 |
20020040417 | Winograd et al. | Apr 2002 | A1 |
20020054594 | Hoof et al. | May 2002 | A1 |
20020054595 | Ambe et al. | May 2002 | A1 |
20020069294 | Herkersdorf et al. | Jun 2002 | A1 |
20020073073 | Cheng | Jun 2002 | A1 |
20020085499 | Toyoyama et al. | Jul 2002 | A1 |
20020087788 | Morris | Jul 2002 | A1 |
20020089937 | Venkatachary et al. | Jul 2002 | A1 |
20020089977 | Chang et al. | Jul 2002 | A1 |
20020091844 | Craft et al. | Jul 2002 | A1 |
20020091884 | Chang et al. | Jul 2002 | A1 |
20020105966 | Patel et al. | Aug 2002 | A1 |
20020126672 | Chow et al. | Sep 2002 | A1 |
20020131437 | Tagore-Brage | Sep 2002 | A1 |
20020141403 | Akahane et al. | Oct 2002 | A1 |
20020146013 | Karlsson et al. | Oct 2002 | A1 |
20020161967 | Kirihata et al. | Oct 2002 | A1 |
20020169786 | Richek | Nov 2002 | A1 |
20020191605 | Van Lunteren et al. | Dec 2002 | A1 |
20030009466 | Ta et al. | Jan 2003 | A1 |
20030012198 | Kaganoi et al. | Jan 2003 | A1 |
20030043800 | Sonksen et al. | Mar 2003 | A1 |
20030043848 | Sonksen | Mar 2003 | A1 |
20030061459 | Aboulenein et al. | Mar 2003 | A1 |
20030074657 | Bramley, Jr. | Apr 2003 | A1 |
20030081608 | Barri et al. | May 2003 | A1 |
20030095548 | Yamano | May 2003 | A1 |
20030103499 | Davis et al. | Jun 2003 | A1 |
20030103500 | Menon et al. | Jun 2003 | A1 |
20030108052 | Inoue et al. | Jun 2003 | A1 |
20030110180 | Calvignac et al. | Jun 2003 | A1 |
20030115403 | Bouchard et al. | Jun 2003 | A1 |
20030120861 | Calle et al. | Jun 2003 | A1 |
20030128668 | Yavatkar et al. | Jul 2003 | A1 |
20030137978 | Kanetake | Jul 2003 | A1 |
20030152084 | Lee et al. | Aug 2003 | A1 |
20030152096 | Chapman | Aug 2003 | A1 |
20030156586 | Lee et al. | Aug 2003 | A1 |
20030159086 | Arndt | Aug 2003 | A1 |
20030165160 | Minami et al. | Sep 2003 | A1 |
20030169470 | Alagar et al. | Sep 2003 | A1 |
20030177221 | Ould-Brahim et al. | Sep 2003 | A1 |
20030198182 | Pegrum et al. | Oct 2003 | A1 |
20030200343 | Greenblat et al. | Oct 2003 | A1 |
20030214956 | Navada et al. | Nov 2003 | A1 |
20030223424 | Anderson et al. | Dec 2003 | A1 |
20030223466 | Noronha, Jr. et al. | Dec 2003 | A1 |
20030227943 | Hallman et al. | Dec 2003 | A1 |
20040022263 | Zhao et al. | Feb 2004 | A1 |
20040028060 | Kang | Feb 2004 | A1 |
20040054867 | Stravers et al. | Mar 2004 | A1 |
20040062245 | Sharp et al. | Apr 2004 | A1 |
20040062246 | Boucher et al. | Apr 2004 | A1 |
20040088469 | Levy | May 2004 | A1 |
20040128434 | Khanna et al. | Jul 2004 | A1 |
20040141504 | Blanc | Jul 2004 | A1 |
20040179548 | Chang et al. | Sep 2004 | A1 |
20040190547 | Gordy et al. | Sep 2004 | A1 |
20040208177 | Ogawa | Oct 2004 | A1 |
20040208181 | Clayton et al. | Oct 2004 | A1 |
20040223502 | Wybenga et al. | Nov 2004 | A1 |
20040235480 | Rezaaifar et al. | Nov 2004 | A1 |
20040264380 | Kalkunte et al. | Dec 2004 | A1 |
20050010630 | Doering et al. | Jan 2005 | A1 |
20050010849 | Ryle et al. | Jan 2005 | A1 |
20050041684 | Reynolds et al. | Feb 2005 | A1 |
20050089049 | Chang et al. | Apr 2005 | A1 |
20050097432 | Obuchi et al. | May 2005 | A1 |
20050132132 | Rosenbluth et al. | Jun 2005 | A1 |
20050132179 | Glaum et al. | Jun 2005 | A1 |
20050138276 | Navada et al. | Jun 2005 | A1 |
20050144369 | Jaspers | Jun 2005 | A1 |
20050152324 | Benveniste | Jul 2005 | A1 |
20050152335 | Lodha et al. | Jul 2005 | A1 |
20050175018 | Wong | Aug 2005 | A1 |
20050185577 | Sakamoto et al. | Aug 2005 | A1 |
20050185652 | Iwamoto | Aug 2005 | A1 |
20050193316 | Chen | Sep 2005 | A1 |
20050201387 | Willis | Sep 2005 | A1 |
20050226236 | Klink | Oct 2005 | A1 |
20050246508 | Shaw | Nov 2005 | A1 |
20050249124 | Elie-Dit-Cosaque et al. | Nov 2005 | A1 |
20060031610 | Liav et al. | Feb 2006 | A1 |
20060034452 | Tonomura | Feb 2006 | A1 |
20060050690 | Epps et al. | Mar 2006 | A1 |
20060077891 | Smith et al. | Apr 2006 | A1 |
20060092829 | Brolin et al. | May 2006 | A1 |
20060092929 | Chun | May 2006 | A1 |
20060114876 | Kalkunte | Jun 2006 | A1 |
20060146374 | Ng et al. | Jul 2006 | A1 |
20060165089 | Klink | Jul 2006 | A1 |
20060209685 | Rahman et al. | Sep 2006 | A1 |
20060221841 | Lee et al. | Oct 2006 | A1 |
20060268680 | Roberts et al. | Nov 2006 | A1 |
20070038798 | Bouchard et al. | Feb 2007 | A1 |
20070088974 | Chandwani et al. | Apr 2007 | A1 |
20070127464 | Jain et al. | Jun 2007 | A1 |
20070179909 | Channasagara | Aug 2007 | A1 |
20070208876 | Davis | Sep 2007 | A1 |
20070253420 | Chang | Nov 2007 | A1 |
20070258475 | Chinn et al. | Nov 2007 | A1 |
20070288690 | Wang et al. | Dec 2007 | A1 |
20080002707 | Davis | Jan 2008 | A1 |
20080031263 | Ervin et al. | Feb 2008 | A1 |
20080037544 | Yano et al. | Feb 2008 | A1 |
20080049742 | Bansal | Feb 2008 | A1 |
20080069125 | Reed et al. | Mar 2008 | A1 |
20080092020 | Hasenplaugh et al. | Apr 2008 | A1 |
20080095169 | Chandra et al. | Apr 2008 | A1 |
20080117075 | Seddigh et al. | May 2008 | A1 |
20080181103 | Davies | Jul 2008 | A1 |
20080205407 | Chang et al. | Aug 2008 | A1 |
20080307288 | Ziesler et al. | Dec 2008 | A1 |
20090175178 | Yoon et al. | Jul 2009 | A1 |
20090279423 | Suresh et al. | Nov 2009 | A1 |
20090279440 | Wong et al. | Nov 2009 | A1 |
20090279441 | Wong et al. | Nov 2009 | A1 |
20090279541 | Wong et al. | Nov 2009 | A1 |
20090279542 | Wong et al. | Nov 2009 | A1 |
20090279546 | Davis | Nov 2009 | A1 |
20090279548 | Davis et al. | Nov 2009 | A1 |
20090279549 | Ramanathan et al. | Nov 2009 | A1 |
20090279558 | Davis et al. | Nov 2009 | A1 |
20090279559 | Wong et al. | Nov 2009 | A1 |
20090279561 | Chang et al. | Nov 2009 | A1 |
20090282148 | Wong et al. | Nov 2009 | A1 |
20090287952 | Patel et al. | Nov 2009 | A1 |
20090290499 | Patel et al. | Nov 2009 | A1 |
20100034215 | Patel et al. | Feb 2010 | A1 |
20100046521 | Wong | Feb 2010 | A1 |
20100061393 | Wong | Mar 2010 | A1 |
20100100671 | Singh | Apr 2010 | A1 |
20100135313 | Davis | Jun 2010 | A1 |
20100161894 | Singh | Jun 2010 | A1 |
20100246588 | Davis | Sep 2010 | A1 |
20100293327 | Lin et al. | Nov 2010 | A1 |
20110002340 | Davis | Jan 2011 | A1 |
20110044340 | Bansal et al. | Feb 2011 | A1 |
20110069711 | Jha et al. | Mar 2011 | A1 |
Number | Date | Country |
---|---|---|
1380127 | Jan 2004 | EP |
2003-289359 | Oct 2003 | JP |
2004-537871 | Dec 2004 | JP |
WO 0184728 | Nov 2001 | WO |
WO 0241544 | May 2007 | WO |
Number | Date | Country | |
---|---|---|---|
20090282322 A1 | Nov 2009 | US |