Error protection for associative memory entries and lookup operations performed thereon

TECHNICAL FIELD

One embodiment of the invention relates to communications and computer systems, especially networked routers, packet switching systems, and other devices; and more particularly, one embodiment relates to error protection for associative memory entries and lookup operations performed thereon.

BACKGROUND

The communications industry is rapidly changing to adjust to emerging technologies and ever increasing customer demand. This customer demand for new applications and increased performance of existing applications is driving communications network and system providers to employ networks and systems having greater speed and capacity (e.g., greater bandwidth). In trying to achieve these goals, a common approach taken by many communications providers is to use packet switching technology. Increasingly, public and private communications networks are being built and expanded using various packet technologies, such as Internet Protocol (IP). Note, nothing described or referenced in this document is admitted as prior art to this application unless explicitly so stated.

A network device, such as a switch or router, typically receives, processes, and forwards or discards a packet based on one or more criteria, including the type of protocol used by the packet, addresses of the packet (e.g., source, destination, group), and type or quality of service requested. Additionally, one or more security operations are typically performed on each packet. But before these operations can be performed, a packet classification operation must typically be performed on the packet.

Packet classification as required for, inter alia, access control lists (ACLs) and forwarding decisions, is a demanding part of switch and router design. The packet classification of a received packet is increasingly becoming more difficult due to ever increasing packet rates and number of packet classifications. For example, ACLs require matching packets on a subset of fields of the packet flow label, with the semantics of a sequential search through the ACL rules. IP forwarding requires a longest prefix match.

Known approaches of packet classification include using custom application-specific integrated circuits (ASICs), custom circuitry, software or firmware controlled processors, and associative memories, including, but not limited to binary content-addressable memories (binary CAMs) and ternary content-addressable memories (ternary CAMs or TCAMs). Each entry of a binary CAM typically includes a value for matching against, while each TCAM entry typically includes a value and a mask. The associative memory compares a lookup word against all of the entries in parallel, and typically generates an indication of the highest priority entry that matches the lookup word. An entry matches the lookup word in a binary CAM if the lookup word and the entry value are identical, while an entry matches the lookup word in a TCAM if the lookup word and the entry value are identical in the bits that are not indicated by the mask as being irrelevant to the comparison operations.

Associative memories are very useful in performing packet classification operations. As with most any system, errors can occur. For example, array parity errors can occur in certain content-addressable memories as a result of failure-in-time errors which are typical of semiconductor devices.

A prior approach protects the associative memory entries with error detection or correction values when the associative memory is not being used to perform a lookup operation. For example, using a background operation, the associative memory entries are periodically checked and corrected for errors (e.g., read from their location and if an error, the correct value is written back). Another prior approach is to periodically over write each associative memory entry with the correct value. These and other prior approaches do not immediately detect the error, nor detect the error when a lookup operation is performed on the corrupted entry. Thus, there can be significant periods (e.g., several seconds to minutes which can be a very long time in the context of a packet switch) before such corrupted entry is corrected.

When a packet classification lookup operation is performed on an associative memory with corrupted entries, a bit error in an entry can result in a false hit, or a false miss. A false hit occurs when the corrupted value of an entry matches the lookup value when it otherwise would not match that entry (and thus another entry or no entry should have been match). A false miss occurs when an entry should have been matched except for the corruption in the entry. This could result in no entry being matched or another lower-priority entry being match. When these lookup operations are used for packet classification, an incorrect match or miss presents a problem especially when identifying a route or performing a security classification. Desired is a mechanism to reduce or eliminate the possible false hits or misses due to corrupted associative memory entries.

SUMMARY

Error protection is provided for associative memory entries and lookup operations performed thereon. Protected associative memory entries are determined which include one or more protection bits. These protected entries are programmed into an associative memory, typically with each protected entry being programmed into two or more consecutive locations. Corresponding protected lookup words are generated and used to perform lookup operations in the associative memory. For binary content-addressable memories (CAMs) and ternary content-addressable memory (TCAMs), one or more error detection bits are used per entry to prevent or at least reduce the possibility of a lookup error. For example, a single parity bit or multiple error-correction code (ECC) bits may be used per entry. The use of the protection bit or bits reduces the possibility of a false matching of a corrupted entry, and the duplicate entries reduce the possibility of not matching an entry that should be matched as all copies of the entry must be corrupt in order to not match one of the entries during a lookup operation.

One embodiment identifies multiple masks used for multiple associative memory entries. A protected entry for each entry in the multiple associative memory entries is determined. Each entry includes an original data portion and an original mask portion. Each determined protected entry includes a protected data portion and a protected mask portion. The protected data portion includes the original data portion and a protection bit located at a bit position corresponding to the original mask portion. The protected mask portion includes the original mask portion and a mask to enable the protection bit corresponding to the original mask portion and to mask protection bits corresponding to other masks of the multiple masks. The protection bit is determined by a parity or other error protection calculation on a result of the original data portion masked with the original mask portion.

In one embodiment, an associative memory is programmed with each of the protected entries. In one embodiment, each of the protective entries is programmed in two consecutive locations in the associative memory. In one embodiment, a lookup operation based on a protected lookup word is performed in the associative memory. In one embodiment, the protected lookup word includes a lookup word original data portion and a lookup word protected data portion. The lookup word protected data portion typically includes multiple bits, with each of the multiple bits being determined by a parity or other error protection calculation on a result of the lookup word original data portion masked with a different one of the multiple masks. In one embodiment, there are n multiple masks and the lookup word protected data portion has n bits.

One embodiment determines a protected entry for each original entry of multiple original associative memory entries, with the protected entry including the original entry and one or more protection bits. The one or more protection bits are determined by a parity or other error protection calculation on the original entry. An associative memory is programmed with each of the determined protected entries. In one embodiment, each of the determined protected entries are programmed in two consecutive locations in the associative memory. In one embodiment, a protected lookup value is determined based on an original lookup value. The protected lookup value includes the original lookup value and one or more protection bits determined by the parity or other error protection calculation on the original lookup value. A lookup operation is performed in the associative memory based on the protected lookup value.

In one embodiment, a lookup operation is performed in the associative memory based on a protected lookup word. In one embodiment, the protected lookup word includes a lookup word original data portion and a lookup word protected data portion. The lookup word protected data portion includes multiple bits, each of the multiple bits is determined by a parity or other error protection calculation on a result of the lookup word original data portion masked with a different one of the multiple masks. In one embodiment, there are n multiple masks and the lookup word protected data portion has n bits.

One embodiment determines a protected lookup word based on a lookup word. The lookup word includes a lookup word original data portion. The protected lookup word includes the lookup word original data portion and multiple error protection bits. Each of the multiple protection bits corresponds to one of multiple masks and is determined by a parity or other error protection calculation on a result of the original data portion masked with a different one of the multiple masks. A lookup operation is performed in the associative memory based on the protected data word.

One embodiment includes a protected lookup word generator and an associative memory. The protected lookup word generator for determining a protected lookup word, the protected lookup word generator is configured to receive a lookup word. The lookup word includes a lookup word original data portion. The protected lookup word includes the lookup word original data portion and multiple error protection bits, with each of the multiple protection bits corresponding to one of multiple masks and is determined by a parity or other error protection calculation on a result of the original data portion masked with a different one of the multiple masks. The associative memory is configured to receive the protected lookup word and to generate an associative memory result based on the protected lookup word.

One embodiment includes a protective associative memory entry generator configured to determine a protected entry for each entry in multiple associative memory entries. Each entry includes an original data portion and an original mask portion. The protected entry includes a protected data portion and a protected mask portion. The protected data portion includes the original data portion and a protection bit located at a bit position corresponding to the original mask portion. The protected mask portion includes the original mask portion and a mask to enable the protection bit corresponding to the original mask portion and to mask protection bits corresponding to other masks of the multiple masks. The protection bit is determined by a parity or other error protection calculation on a result of the original data portion masked with the original mask portion. The associative memory is programmed with the determined protected entry for each entry in the multiple associative memory entries.

BRIEF DESCRIPTION OF THE DRAWINGS

The appended claims set forth the features of the invention with particularity. The invention, together with its advantages, may be best understood from the following detailed description taken in conjunction with the accompanying drawings of which:

<figref idref="DRAWINGS">FIG. 1A</figref> is a block diagram illustrating the generation of protected entries used in one embodiment;

<figref idref="DRAWINGS">FIG. 1B</figref> is a flow diagram illustrating a process used in one embodiment for generating protected entries;

<figref idref="DRAWINGS">FIG. 1C</figref> is a block diagram illustrating exemplary programming of an associative memory with protected entries;

<figref idref="DRAWINGS">FIG. 2A</figref> is a block diagram illustrating the generation of a protected lookup value used in one embodiment;

<figref idref="DRAWINGS">FIG. 2B</figref> is a flow diagram illustrating a process used in one embodiment for generating protected lookup values;

<figref idref="DRAWINGS">FIG. 3A</figref> is a block diagram illustrating the generation of protected entries used in one embodiment;

<figref idref="DRAWINGS">FIG. 3B</figref> is a flow diagram illustrating a process used in one embodiment for generating protected entries;

<figref idref="DRAWINGS">FIG. 4A</figref> is a block diagram illustrating the generation of a protected lookup value used in one embodiment;

<figref idref="DRAWINGS">FIG. 4B</figref> is a flow diagram illustrating a process used in one embodiment for generating protected lookup values;

<figref idref="DRAWINGS">FIG. 5A</figref> is a block diagram illustrating an embodiment for generating and programming an associative memory with protected entries and performing lookup operations thereon using generated protected lookup values; and

<figref idref="DRAWINGS">FIG. 5B</figref> is a block illustrating a system or component used in one embodiment for generating and/or programming an associative memory with protected entries and/or performing lookup operations thereon using generated protected lookup values.

DETAILED DESCRIPTION

Disclosed are, inter alia, methods, apparatus, data structures, computer-readable media, mechanisms, and means for providing error protection for associative memory entries and lookup operations performed thereon.

Embodiments described herein include various elements and limitations, with no one element or limitation contemplated as being a critical element or limitation. Each of the claims individually recites an aspect of the invention in its entirety. Moreover, some embodiments described may include, but are not limited to, inter alia, systems, networks, integrated circuit chips, embedded processors, ASICs, methods, and computer-readable media containing instructions. One or multiple systems, devices, components, etc. may comprise one or more embodiments, which may include some elements or limitations of a claim being performed by the same or different systems, devices, components, etc. The embodiments described hereinafter embody various aspects and configurations within the scope and spirit of the invention, with the figures illustrating exemplary and non-limiting configurations.

As used herein, the term “packet” refers to packets of all types or any other units of information or data, including, but not limited to, fixed length cells and variable length packets, each of which may or may not be divisible into smaller packets or cells. The term “packet” as used herein also refers to both the packet itself or a packet indication, such as, but not limited to all or part of a packet or packet header, a data structure value, pointer or index, or any other part or direct or indirect identification of a packet or information associated therewith. For example, often times a router operates on one or more fields of a packet, especially the header, so the body of the packet is often stored in a separate memory while the packet header is manipulated, and based on the results of the processing of the packet (i.e., the packet header in this example), the entire packet is forwarded or dropped, etc. Additionally, these packets may contain one or more types of information, including, but not limited to, voice, data, video, and audio information. The term “item” is used generically herein to refer to a packet or any other unit or piece of information or data, a device, component, element, or any other entity. The phrases “processing a packet” and “packet processing” typically refer to performing some steps or actions based on the packet contents (e.g., packet header or other fields), and such steps or action may or may not include modifying, storing, dropping, and/or forwarding the packet and/or associated data.

The term “system” is used generically herein to describe any number of components, elements, sub-systems, devices, packet switch elements, packet switches, routers, networks, computer and/or communication devices or mechanisms, or combinations of components thereof. The term “computer” is used generically herein to describe any number of computers, including, but not limited to personal computers, embedded processing elements and systems, control logic, ASICs, chips, workstations, mainframes, etc. The term “processing element” is used generically herein to describe any type of processing mechanism or device, such as a processor, ASIC, field programmable gate array, computer, etc. The term “device” is used generically herein to describe any type of mechanism, including a computer or system or component thereof. The terms “task” and “process” are used generically herein to describe any type of running program, including, but not limited to a computer process, task, thread, executing application, operating system, user process, device driver, native code, machine or other language, etc., and can be interactive and/or non-interactive, executing locally and/or remotely, executing in foreground and/or background, executing in the user and/or operating system address spaces, a routine of a library and/or standalone application, and is not limited to any particular memory partitioning technique. The steps, connections, and processing of signals and information illustrated in the figures, including, but not limited to any block and flow diagrams and message sequence charts, may typically be performed in the same or in a different serial or parallel ordering and/or by different components and/or processes, threads, etc., and/or over different connections and be combined with other functions in other embodiments, unless this disables the embodiment or a sequence is explicitly or implicitly required (e.g., for a sequence of read the value, process the value—the value must be obtained prior to processing it, although some of the associated processing may be performed prior to, concurrently with, and/or after the read operation). Furthermore, the term “identify” is used generically to describe any manner or mechanism for directly or indirectly ascertaining something, which may include, but is not limited to receiving, retrieving from memory, determining, defining, calculating, generating, etc.

Moreover, the terms “network” and “communications mechanism” are used generically herein to describe one or more networks, communications media or communications systems, including, but not limited to the Internet, private or public telephone, cellular, wireless, satellite, cable, local area, metropolitan area and/or wide area networks, a cable, electrical connection, bus, etc., and internal communications mechanisms such as message passing, interprocess communications, shared memory, etc. The term “message” is used generically herein to describe a piece of information which may or may not be, but is typically communicated via one or more communication mechanisms of any type.

The term “storage mechanism” includes any type of memory, storage device or other mechanism for maintaining instructions or data in any format. “Computer-readable medium” is an extensible term including any memory, storage device, storage mechanism, and other storage and signaling mechanisms including interfaces and devices such as network interface cards and buffers therein, as well as any communications devices and signals received and transmitted, and other current and evolving technologies that a computerized system can interpret, receive, and/or transmit. The term “memory” includes any random access memory (RAM), read only memory (ROM), flash memory, integrated circuits, and/or other memory components or elements. The term “storage device” includes any solid state storage media, disk drives, diskettes, networked services, tape drives, and other storage devices. Memories and storage devices may store computer-executable instructions to be executed by a processing element and/or control logic, and data which is manipulated by a processing element and/or control logic. The term “data structure” is an extensible term referring to any data element, variable, data structure, database, and/or one or more organizational schemes that can be applied to data to facilitate interpreting the data or performing operations on it, such as, but not limited to memory locations or devices, sets, queues, trees, heaps, lists, linked lists, arrays, tables, pointers, etc. A data structure is typically maintained in a storage mechanism. The terms “pointer” and “link” are used generically herein to identify some mechanism for referencing or identifying another element, component, or other entity, and these may include, but are not limited to a reference to a memory or other storage mechanism or location therein, an index in a data structure, a value, etc. The term “associative memory” is an extensible term, and refers to all types of known or future developed associative memories, including, but not limited to binary and ternary content addressable memories, hash tables, TRIE and other data structures, etc. Additionally, the term “associative memory unit” may include, but is not limited to one or more associative memory devices or parts thereof, including, but not limited to regions, segments, banks, pages, blocks, sets of entries, etc.

The term “one embodiment” is used herein to reference a particular embodiment, wherein each reference to “one embodiment” may refer to a different embodiment, and the use of the term repeatedly herein in describing associated features, elements and/or limitations does not establish a cumulative set of associated features, elements and/or limitations that each and every embodiment must include, although an embodiment typically may include all these features, elements and/or limitations. In addition, the phrase “means for xxx” typically includes computer-readable media containing computer-executable instructions for performing xxx.

In addition, the terms “first,” “second,” etc. are typically used herein to denote different units (e.g., a first element, a second element). The use of these terms herein does not necessarily connote an ordering such as one unit or event occurring or coming before another, but rather provides a mechanism to distinguish between particular units. Additionally, the use of a singular tense of a noun is non-limiting, with its use typically including one or more of the particular thing rather than just one (e.g., the use of the word “memory” typically refers to one or more memories without having to specify “memory or memories,” or “one or more memories” or “at least one memory”, etc.). Moreover, the phrases “based on x” and “in response to x” are used to indicate a minimum set of items x from which something is derived or caused, wherein “x” is extensible and does not necessarily describe a complete list of items on which the operation is performed, etc. Additionally, the phrase “coupled to” is used to indicate some level of direct or indirect connection between two elements or devices, with the coupling device or devices modifying or not modifying the coupled signal or communicated information. The term “subset” is used to indicate a group of all or less than all of the elements of a set. The term “subtree” is used to indicate all or less than all of a tree. Moreover, the term “or” is used herein to identify a selection of one or more, including all, of the conjunctive items.

Error protection is provided for associative memory entries and lookup operations performed thereon. Protected associative memory entries are determined which include one or more protection bits. These protected entries are programmed into an associative memory, typically with each protected entry being programmed into two or more consecutive locations. Corresponding protected lookup words are generated and used to perform lookup operations in the associative memory. For binary content-addressable memories (CAMs) and ternary content-addressable memory (TCAMs), one or more error detection bits are used per entry to prevent or at least reduce the possibility of a lookup error. For example, a single parity bit or multiple error-correction code (ECC) bits may be used per entry. The use of the protection bit or bits reduces the possibility of a false matching of a corrupted entry, and the duplicate entries reduce the possibility of not matching an entry that should be matched as all copies of the entry must be corrupt in order to not match one of the entries during a lookup operation. For example, when a TCAM is used for determining IPv4 routes, one router typically uses approximately a dozen different prefixes. In a worst case scenario, one embodiment uses as many error protection bits as there are bits in the mask of an entry.

One embodiment identifies multiple masks used for multiple associative memory entries. A protected entry for each entry in the multiple associative memory entries is determined. Each entry includes an original data portion and an original mask portion.

Each determined protected entry includes a protected data portion and a protected mask portion. The protected data portion includes the original data portion and a protection bit located at a bit position corresponding to the original mask portion. The protected mask portion includes the original mask portion and a mask to enable the protection bit corresponding to the original mask portion and to mask protection bits corresponding to other masks of the multiple masks. The protection bit is determined by a parity or other error protection calculation on a result of the original data portion masked with the original mask portion.

In one embodiment, an associative memory is programmed with each of the protected entries. In one embodiment, each of the protective entries is programmed in two consecutive locations in the associative memory. In one embodiment, a lookup operation based on a protected lookup word is performed in the associative memory. In one embodiment, the protected lookup word includes a lookup word original data portion and a lookup word protected data portion. The lookup word protected data portion typically includes multiple bits, with each of the multiple bits being determined by a parity or other error protection calculation on a result of the lookup word original data portion masked with a different one of the multiple masks. In one embodiment, there are n multiple masks and the lookup word protected data portion has n bits.

One embodiment determines a protected entry for each original entry of multiple original associative memory entries, with the protected entry including the original entry and one or more protection bits. The one or more protection bits are determined by a parity or other error protection calculation on the original entry. An associative memory is programmed with each of the determined protected entries. In one embodiment, each of the determined protected entries are programmed in two consecutive locations in the associative memory. In one embodiment, a protected lookup value is determined based on an original lookup value. The protected lookup value includes the original lookup value and one or more protection bits determined by the parity or other error protection calculation on the original lookup value. A lookup operation is performed in the associative memory based on the protected lookup value.

In one embodiment, a lookup operation is performed in the associative memory based on a protected lookup word. In one embodiment, the protected lookup word includes a lookup word original data portion and a lookup word protected data portion. The lookup word protected data portion includes multiple bits, each of the multiple bits is determined by a parity or other error protection calculation on a result of the lookup word original data portion masked with a different one of the multiple masks. In one embodiment, there are n multiple masks and the lookup word protected data portion has n bits.

One embodiment determines a protected lookup word based on a lookup word. The lookup word includes a lookup word original data portion. The protected lookup word includes the lookup word original data portion and multiple error protection bits. Each of the multiple protection bits corresponds to one of multiple masks and is determined by a parity or other error protection calculation on a result of the original data portion masked with a different one of the multiple masks. A lookup operation is performed in the associative memory based on the protected data word.

One embodiment includes a protected lookup word generator and an associative memory. The protected lookup word generator for determining a protected lookup word, the protected lookup word generator is configured to receive a lookup word. The lookup word includes a lookup word original data portion. The protected lookup word includes the lookup word original data portion and multiple error protection bits, with each of the multiple protection bits corresponding to one of multiple masks and is determined by a parity or other error protection calculation on a result of the original data portion masked with a different one of the multiple masks. The associative memory is configured to receive the protected lookup word and to generate an associative memory result based on the protected lookup word.

One embodiment includes a protective associative memory entry generator configured to determine a protected entry for each entry in multiple associative memory entries. Each entry includes an original data portion and an original mask portion. The protected entry includes a protected data portion and a protected mask portion. The protected data portion includes the original data portion and a protection bit located at a bit position corresponding to the original mask portion. The protected mask portion includes the original mask portion and a mask to enable the protection bit corresponding to the original mask portion and to mask protection bits corresponding to other masks of the multiple masks. The protection bit is determined by a parity or other error protection calculation on a result of the original data portion masked with the original mask portion. The associative memory is programmed with the determined protected entry for each entry in the multiple associative memory entries.

Turning to the figures, <figref idref="DRAWINGS">FIG. 1A</figref> illustrates the generation of protected entries performed in one embodiment. As shown, protected entry <b>120</b> includes and/or comprises a protected data portion <b>121</b> and a protected mask portion <b>122</b>. Protected data portion <b>121</b> includes and/or comprises original data portion <b>123</b> and protection data bits <b>124</b>. Protected mask portion includes and/or comprises original mask portion <b>125</b> and protection mask <b>126</b>.

Original entry <b>100</b> (e.g., a typically TCAM entry including a data portion and mask portion) includes an original data portion <b>101</b> and an original mask portion <b>102</b>. A mask position identifier <b>110</b> identifies a bit position corresponding to original mask portion <b>102</b>. This can be performed in an unlimited different manners, such as, but not limited to a lookup operation in a table, array or content-addressable memory, a calculation, etc. Selector function <b>111</b> then enables (set or clears) the bit corresponding to the identified bit position to matter, and causes (clears or sets) all other bit positions in protection mask <b>126</b> to be mask enabled bits (i.e., to mask all bits not corresponding to the relevant protection bit). Thus, in one embodiment, N protection data bits and N protection mask bits are used for N different original masks (e.g., corresponding to original mask portion <b>102</b>). The protected mask portion then includes and/or comprises the original mask portion <b>125</b> copied from original mask portion <b>102</b> and the protection mask <b>126</b>.

The original data portion <b>123</b> of protected data portion <b>121</b> is copied from original data portion <b>101</b> of original entry <b>100</b>. To determine the value of the relevant protection bit, the original data portion <b>101</b> is masked with the original mask portion <b>102</b> as illustrated by masking function <b>112</b>, and then the protection bit generation function <b>113</b> (e.g., even or odd parity or some other error protection function—i.e., any protection or detection function) produces the protection bit, and is located as illustrated by shifting function <b>114</b> in the bit position within protection data bits <b>124</b> corresponding to the original mask portion <b>102</b> (as determined by mask position identifier <b>110</b>). Note, in one embodiment, the other bits will be masked by protection mask <b>126</b> so they don't matter.

Using protected entry <b>120</b> instead of original entry <b>100</b> provides a mechanism whereby a single corrupted bit in an entry will cause the entry not to match during a lookup operation, which ensures that there is not a false hit on this corrupted entry.

<figref idref="DRAWINGS">FIG. 1C</figref> illustrates exemplary programming of an associative memory with protected entries. In one embodiment, an associative memory <b>180</b> is programmed with the generated protected entries <b>181</b>-<b>189</b>. In one embodiment, an associative memory <b>190</b> is programmed with associative memory entries <b>191</b>-<b>199</b> with each entry programmed two or more times typically in consecutive locations as this significantly reduces the probability of a false miss (i.e., not correctly matching an uncorrupted entry) as all of these same entries must be corrupted in order not to match one of them. Thus, if the first entry of multiple same entries in the search order is not corrupted it will appropriately match or miss. If the first entry (or more entries) of multiple same entries in the search order is corrupted it will be forced to not match the lookup word. Therefore, one of the other same entries (assuming they are all not corrupted) will generate a hit if it matches the protected lookup word, and thus avoid a false miss condition (as occurred because of the corrupted first entry in this example).

<figref idref="DRAWINGS">FIG. 1B</figref> illustrates a process used in one embodiment for generating protected entries. Processing begins with process block <b>140</b>, and proceeds to process block <b>142</b>, wherein the set of used masks is identified. Next, in process block <b>144</b>, one protection bit for each used mask is allocated in the protection data portion and the protected mask portion of the protected entries.

As determined in process block <b>146</b>, while there are more original entries to process, the next original entry to program is identified in process block <b>150</b>. Then, in process block <b>152</b>, the corresponding protection bit position is determined based on the mask of the original entry (e.g., via a table lookup operation, a calculation, etc.). In process block <b>154</b>, the original data portion is masked with the original mask portion of the current original entry, and the value of the protection bit is determined based on the masked result. In process block <b>156</b>, the protected entry including the protected data and mask portions is generated. The protected data portion includes the original data portion and the determined protection bit at the corresponding protection bit position. The protected mask portion includes the original protected mask portion and a mask to mask all bits in the protection data portion except the protection bit in the corresponding protection bit position. Next, in process block <b>158</b>, one or more consecutive entries (typically two) in the associative memory are programmed with the generated protection entry. In one embodiment, all the protection entries are first generated, and subsequently the protection entries are programmed into the associative memory. Processing of the flow diagram returns to process block <b>146</b>, to determine if there are more original entries to process. When all original entries have been processed, processing is complete as indicated by process block <b>148</b>.

<figref idref="DRAWINGS">FIG. 2A</figref> is a block diagram illustrating the generation of a protected lookup value used in one embodiment. Original lookup value <b>200</b> includes an original data portion <b>201</b>, which is replicated into original data portion <b>223</b> of the generated protected lookup value <b>220</b> and protected data portion <b>221</b>, which also includes an ordered set of protection data bits <b>224</b>, one for each of the possible masks used to mask an associative memory entry.

One embodiment generates these protection data bits by sequencing through each of the possible masks, determining the corresponding value of the protection bit, and storing it in the proper bit position within field <b>224</b>.

One embodiment does this by using a counter <b>210</b> to sequence through the possible masks stored in mask memory <b>211</b>. A masking function <b>212</b> then masks the original lookup values <b>200</b> with the mask. Protection bit generator <b>213</b> determines the value of the protection bit to used, and shifting function <b>214</b> based on counter <b>210</b> positions the generated protection bit into the proper bit position within field <b>224</b>.

<figref idref="DRAWINGS">FIG. 2B</figref> is a flow diagram illustrating a process used in one embodiment for generating protected lookup values. Processing begins with process block <b>240</b>, and proceeds to process block <b>242</b>, wherein an original lookup value is identified and replicated in the protected lookup value. While there are more possible masks as determined in process block <b>244</b>, a next particular one of the masks is identified in process block <b>246</b>. In process block <b>248</b>, the original lookup values is masked with the particular mask, with the value of the protection bit being determined based on the mask result. In process block <b>250</b>, the determined protection bit is stored in the corresponding position in the protected bit portion of the protected lookup value being generated.

After all protection bits have been generated and added to the original lookup value to generate the protected lookup value as determined in process block <b>244</b>, the lookup operation is performed in process block <b>260</b> on the set of protected lookup entries. Processing is complete as indicated by process block <b>262</b>.

Note, one embodiment uses a set of multiple protection bits per mask in place of the single bit described in relation to <figref idref="DRAWINGS">FIGS. 1A-B</figref> and <b>2</b>A-B, as the increased number of protection bits provides enhanced error detection, but at a cost of more bits per entry.

<figref idref="DRAWINGS">FIGS. 3A</figref>, <b>3</b>B, <b>4</b>A and <b>4</b>C illustrate the generation of protected associative memory entries and lookup values when each entry is not masked, such as those entries typically used in a binary content-addressable memory.

<figref idref="DRAWINGS">FIG. 3A</figref> illustrates the generation of protected entries used in one embodiment. Original entry <b>300</b> includes an original data portion <b>301</b>, which is replicated in original data portion <b>323</b> of protected entry <b>320</b>. One or more protection bits (e.g., even or odd parity or some other error protection function—i.e., any protection or detection function) are determined by protection bit(s) generation function <b>313</b> and placed in field <b>324</b>. Protected entry <b>320</b> and protected data portion <b>321</b> thus includes and/or consists of original data portion <b>323</b> and one or more protection data bits <b>324</b>.

<figref idref="DRAWINGS">FIG. 3B</figref> illustrates a process used in one embodiment for generating protected entries. Processing begins with process block <b>340</b>, and proceeds to process block <b>342</b>, wherein one or more data protection bits are allocated in each protected entry. While there are more original entries to process as determined in process block <b>344</b>, the next original entry is identified in process block <b>350</b>. In process block <b>352</b>, the corresponding one or more protection bits are determined based on the original entry. In process block <b>354</b>, the protected entry is generated including the protected data portions, the protected data portions including the original data portion and the determined one or more protection bits. Next, in process block <b>356</b>, one or more consecutive entries (typically two) in the associative memory are programmed with the generated protection entry. (In one embodiment, all the protection entries are first generated, and subsequently the protection entries are programmed into the associative memory.) Processing of the flow diagram returns to process block <b>344</b>, to determine if there are more original entries to process. When all original entries have been processed, processing is complete as indicated by process block <b>346</b>.

<figref idref="DRAWINGS">FIG. 4A</figref> illustrates the generation of a protected lookup value used in one embodiment. An original lookup value <b>400</b> is identified. Original lookup value includes the original data portion <b>401</b>, which is replicated in original data portion <b>423</b> of protected lookup value <b>420</b>. One or more protection data bits are determined by protection bit(s) generator <b>413</b>, and placed in one or more protection data bits <b>424</b> of the generated protected lookup value <b>420</b>. Protected lookup value <b>420</b> and protected data portion <b>421</b> thus includes and/or consists of original data portion <b>423</b> and one or more protection data bits <b>424</b>.

<figref idref="DRAWINGS">FIG. 4B</figref> illustrates a process used in one embodiment for generating protected lookup values. Processing begins with process block <b>440</b>, and proceeds to process block <b>442</b>, wherein the original lookup value is identified and stored in the protected lookup value being generated. In process block <b>444</b>, the one or more protection bits are determined for the original lookup value. In process block <b>446</b>, the one or more protection bits are stored in the generated protected lookup value. In process block <b>448</b>, a lookup operation is performed on the protected entries based on the protected lookup value. Processing is complete as indicated by process block <b>450</b>.

<figref idref="DRAWINGS">FIG. 5A</figref> is a block diagram illustrating a system with protected associative memory entries <b>500</b>, which generates and programs an associative memory with protected entries and performs lookup operations thereon using the generated protected lookup values. System <b>500</b> may be part of a router, communications, computer or any other system or component.

In one embodiment, control logic <b>510</b> generates protected entries, programs, updates, generates protected lookup values and performs lookup operations on associative memory or memories <b>512</b> by providing updates and protected lookup words <b>511</b>. In one embodiment, control logic <b>510</b> includes custom circuitry, such as, but not limited to discrete circuitry, ASICs, memory devices, processors, etc. Control logic <b>510</b> also typically stores indications of desired actions to be taken via updates <b>514</b> in adjunct memory or memories <b>515</b>. A hit result <b>513</b> is typically provided to control logic <b>510</b> and to adjunct memory or memories <b>515</b>, which produces result <b>516</b>. In one embodiment, a single chip or ASIC contains system <b>500</b>. In one embodiment, a single chip or ASIC contains system <b>500</b> except for packet processor <b>505</b>. In one embodiment, less than all or even no two components of system <b>500</b> reside on the same chip or ASIC.

In one embodiment, packets <b>501</b> are received by packet processor <b>505</b>. In addition to other operations (e.g., packet routing, security, etc.), packet processor <b>505</b> typically generates a lookup value <b>503</b> (either an original or protected lookup value) which is provided to control logic <b>510</b>, which generates the protected lookup value <b>511</b> if required, and initiates one or more associative memory lookup operations on associative memory or memories <b>512</b>. A result <b>507</b> (e.g., a packet classification identification or action) is typically returned to packet processor <b>505</b>, and in response, one or more of the received packets are manipulated and forwarded as indicated by packets <b>509</b>.

<figref idref="DRAWINGS">FIG. 5B</figref> is a block illustrating a system or component used in one embodiment for generating and/or programming an associative memory with protected entries and/or performing lookup operations thereon using generated protected lookup values. System <b>520</b> may be part of a router, communications, computer or any other system or component. In one embodiment, system <b>520</b> performs one or more processes corresponding to one of the diagrams illustrated herein or otherwise described herein.

In one embodiment, system <b>520</b> includes a processing element <b>521</b>, memory <b>522</b>, storage devices <b>523</b>, one or more block mask associative memories <b>524</b>, and an interface <b>525</b> for connecting to other devices, which are coupled via one or more communications mechanisms <b>529</b> (shown as a bus for illustrative purposes).

Various embodiments of system <b>520</b> may include more or less elements. The operation of system <b>520</b> is typically controlled by processing element <b>521</b> using memory <b>522</b> and storage devices <b>523</b> to perform one or more tasks or processes, such as programming and performing protected lookup operations using associative memory or memories <b>524</b>. Memory <b>522</b> is one type of computer readable media, and typically comprises random access memory (RAM), read only memory (ROM), flash memory, integrated circuits, and/or other memory components. Memory <b>522</b> typically stores computer executable instructions to be executed by processing element <b>521</b> and/or data which is manipulated by processing element <b>521</b> for implementing functionality in accordance with one embodiment of the invention. Storage devices <b>523</b> are another type of computer readable media, and typically comprise solid state storage media, disk drives, diskettes, networked services, tape drives, and other storage devices. Storage devices <b>523</b> typically store computer executable instructions to be executed by processing element <b>521</b> and/or data which is manipulated by processing element <b>521</b> for implementing functionality in accordance with one embodiment of the invention.

In one embodiment, processing element <b>521</b> provides control and data information (e.g., lookup words, modification data, profile IDs, etc.) to associative memory or memories <b>524</b>, which perform lookup operations to generate lookup results and possibly error indications, which are received and used by processing element <b>521</b> and/or communicated to other devices via interface <b>525</b>.

In view of the many possible embodiments to which the principles of our invention may be applied, it will be appreciated that the embodiments and aspects thereof described herein with respect to the drawings/figures are only illustrative and should not be taken as limiting the scope of the invention. For example and as would be apparent to one skilled in the art, many of the process block operations can be re-ordered to be performed before, after, or substantially concurrent with other operations. Also, many different forms of data structures could be used in various embodiments. The invention as described herein contemplates all such embodiments as may come within the scope of the following claims and equivalents thereof.