# US 2010/0169673 A1 · Efficient remapping engine utilization > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2010/0169673 A1 - Document ID: US20100169673A1 - Status: Published application - Kind: A1 - Application number: 12/319,060 - Filed: 2008-12-31 - Published: 2010-07-01 - Earliest claimed: 2008-12-31 - Inventors: Ramakrishna Saripalli - Web page: https://patentgrep.com/patent/US20100169673A1 ## CPC - G06F 12/145: {the protection being virtual, e.g. for virtual blocks or segments before a translation mechanism} - G06F 12/1081: for peripheral access to main memory, e.g. direct memory access [DMA] - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A device, system, and method are disclosed. In one embodiment device includes remapping engine reallocation logic that is capable of monitoring a first amount of traffic that is translated by a first remapping engine. If the first amount of traffic reaches the threshold level of the first remapping engine, then the logic will divert a portion of the traffic to be translated by a second remapping engine. ## Claims ### Claim 1 A device, comprising: remapping engine reallocation logic to monitor a first amount of traffic being translated by a first remapping engine; and divert a portion of the first amount of traffic to be translated by a second remapping engine when the first amount of traffic reaches a first remapping engine traffic threshold level. ### Claim 2 (depends on 1) The device of claim 1, wherein the remapping engine reallocation logic is further operable to: prior to diverting the portion of the first amount of traffic, query the second remapping engine to determine an amount of translation capacity available; and allow the diversion when the available amount of translation capacity is capable of servicing the portion of the first amount of traffic to be diverted. ### Claim 3 (depends on 2) The device of claim 2, wherein the remapping engine reallocation logic is further operable to: determine the capacity of the first and second remapping engines; and apportion a portion of the first amount of traffic to each of the first and 2nd remapping engines so that each engine has substantially the same percentage of traffic relative to each engine's maximum capacity. ### Claim 4 (depends on 3) The device of claim 3, wherein the remapping engine reallocation logic is further operable to: divert a portion of the first amount of traffic to one or more additional remapping engines, wherein the first, second, and one or more additional remapping engines each have substantially the same percentage of traffic relative to each engine's maximum capacity. ### Claim 5 (depends on 1) The device of claim 1, wherein the first amount of traffic comprises traffic from at least a first device and a second device. ### Claim 6 (depends on 5) The device of claim 5, wherein the portion of the first amount of traffic diverted to the second remapping engine comprises at least the traffic from at least the second device. ### Claim 7 (depends on 1) The device of claim 1, wherein the remapping engine reallocation logic is further operable to: monitor the first amount of traffic being translated by the first remapping engine and the second remapping engine; and divert the portion of the first amount of traffic being translated by the second remapping engine to the first remapping engine when the first amount of traffic returns below the first traffic threshold level. ### Claim 8 (depends on 7) The device of claim 7, wherein the remapping engine reallocation logic is further operable to: communicate to a power management logic that the second remapping engine can be shut down after the portion of the first amount of traffic being translated by the second remapping engine is diverted back to the first remapping engine. ### Claim 9 A system, comprising: a first device and a second device; a first remapping engine and a second remapping engine, each remapping engine coupled to both the first and second devices; and remapping engine reallocation logic, coupled to both the first and second remapping engines, the remapping engine reallocation logic to monitor a first amount of traffic being translated by a first remapping engine; and divert a portion of the first amount of traffic to be translated by a second remapping engine when the first amount of traffic reaches a first remapping engine traffic threshold level. ### Claim 10 (depends on 9) The system of claim 9, wherein the remapping engine reallocation logic is further operable to: prior to diverting the portion of the first amount of traffic, query the second remapping engine to determine an amount of translation capacity available; and allow the diversion when the available amount of translation capacity is capable of servicing the portion of the first amount of traffic to be diverted. ### Claim 11 (depends on 10) The system of claim 10, wherein the remapping engine reallocation logic is further operable to: determine the capacity of the first and second remapping engines; and apportion a portion of the first amount of traffic to each of the first and 2nd remapping engines so that each engine has substantially the same percentage of traffic relative to each engine's maximum capacity. ### Claim 12 (depends on 11) The system of claim 11, wherein the remapping engine reallocation logic is further operable to: divert a portion of the first amount of traffic to one or more additional remapping engines, wherein the first, second, and one or more additional remapping engines each have substantially the same percentage of traffic relative to each engine's maximum capacity. ### Claim 13 (depends on 9) The system of claim 9, wherein the first amount of traffic comprises traffic from at least the first device and the second device. ### Claim 14 (depends on 13) The system of claim 13, wherein the portion of the first amount of traffic diverted to the second remapping engine comprises at least the traffic from at least the second device. ### Claim 15 (depends on 9) The system of claim 9, wherein the remapping engine reallocation logic is further operable to: monitor the first amount of traffic being translated by the first remapping engine and the second remapping engine; and divert the portion of the first amount of traffic being translated by the second remapping engine to the first remapping engine when the first amount of traffic returns below the first traffic threshold level. ### Claim 16 (depends on 15) The system of claim 15, further comprising: a power management logic to manage the power delivered to at least each of the first and second remapping engines, wherein the remapping engine reallocation logic is further operable to communicate to the power management logic to at least lower the amount of power delivered to the second remapping engine after the portion of the first amount of traffic being translated by the second remapping engine is diverted back to the first remapping engine. ### Claim 17 A method, comprising: monitoring a first amount of traffic being translated by a first remapping engine; and diverting a portion of the first amount of traffic to be translated by a second remapping engine when the first amount of traffic reaches a first remapping engine traffic threshold level. ### Claim 18 (depends on 17) The method of claim 17, further comprising: prior to diverting the portion of the first amount of traffic, querying the second remapping engine to determine an amount of translation capacity available; and allowing the diversion when the available amount of translation capacity is capable of servicing the portion of the first amount of traffic to be diverted. ### Claim 19 (depends on 18) The device of claim 18, further comprising: determining the capacity of the first and second remapping engines; and apportioning a portion of the first amount of traffic to each of the first and 2nd remapping engines so that each engine has substantially the same percentage of traffic relative to each engine's maximum capacity. ### Claim 20 (depends on 19) The device of claim 19, further comprising: diverting a portion of the first amount of traffic to one or more additional remapping engines, wherein the first, second, and one or more additional remapping engines each have substantially the same percentage of traffic relative to each engine's maximum capacity. ### Claim 21 (depends on 17) The device of claim 17, wherein the first amount of traffic comprises traffic from at least a first device and a second device. ### Claim 22 (depends on 21) The device of claim 21, wherein the portion of the first amount of traffic diverted to the second remapping engine comprises at least the traffic from at least the second device. ### Claim 23 (depends on 17) The device of claim 17, further comprising: monitoring the first amount of traffic being translated by the first remapping engine and the second remapping engine; and diverting the portion of the first amount of traffic being translated by the second remapping engine to the first remapping engine when the first amount of traffic returns below the first traffic threshold level. ### Claim 24 (depends on 23) The device of claim 23, further comprising: communicating to a power management logic that the second remapping engine can be shut down after the portion of the first amount of traffic being translated by the second remapping engine is diverted back to the first remapping engine.