1460890883-8d563486-cbe7-4aff-a9c7-b014202c120d

1. A storage device comprising:
a first non-volatile memory;
a second non-volatile memory;
a first controller that controls the first non-volatile memory to cause the first non-volatile memory to perform processes;
a second controller that controls the second non-volatile memory to cause the second non-volatile memory to perform processes; and
a signal line which is connected to the first controller and the second controller and through which a token is transmitted between the first controller and the second controller;
wherein the first controller is capable of controlling the first non-volatile memory while holding the token and the second controller is capable of controlling the second non-volatile memory while holding the token.
2. The storage device according to claim 1,
wherein the first controller determines amount of time to hold the token based on the process which the first controller causes the first non-volatile memory to perform.
3. The storage device according to claim 1,
wherein the first controller determines a timing to transmit the token based on the power consumption transitional characteristics of the process which the first controller causes the first non-volatile memory to perform.
4. The storage device according to claim 3,
wherein the first and second controllers change the power consumption transitional characteristics to a new power consumption transitional characteristics depending on use conditions of the storage device which are changed while the storage device is used.
5. The storage device according to claim 3,
wherein the first controller changes the power consumption transitional characteristics to a new power consumption transitional characteristics depending on the number of erasing operations of the first and second non-volatile memory.
6. The storage device according to claim 3,
wherein the first controller changes the power consumption transitional characteristics to a new power consumption transitional characteristics depending on the number of error correction bits during a reading operation of the first non-volatile memory.
7. The storage device according to claim 3,
wherein the first controller changes the power consumption transitional characteristics to a new power consumption transitional characteristics depending on the time required for process performed by the first non-volatile memory.
8. The storage device according to claim 1,
wherein the first controller determines a timing to transmit the token based on the type of process which the first controller causes the first non-volatile memory to perform.
9. The storage device according to claim 1,
wherein the first controller transmits the token to the second controller after the first controller causes the first non-volatile memory to perform the process when the sum of power consumption of the first non-volatile memory and estimated power consumption of the second non-volatile memory is less than a predetermined amount.
10. The storage device according to claim 1,
wherein, when the token is received, the first controller causes the first non-volatile memory to perform the process, and
the first controller transmits the token to the second controller at a time when a transition of power consumption generated by the process of the first non-volatile memory is below a first threshold value.
11. The storage device according to claim 1, further comprising:
a third non-volatile memory; and
a third controller that controls the third non-volatile memory to cause the third non-volatile memory to perform processes,
wherein the signal line is further connected to the third controller and at least two tokens are transmitted between the first controller, second controller and third controller through the signal line.
12. The storage device according to claim 1,
wherein the first and second controllers change to a first low power consumption mode while they do not holding the token.
13. The storage device according to claim 12,
wherein the first and second controllers further change from the first low power consumption mode to a second low power consumption mode while they do not hold the token.
14. The storage device according to claim 1, further comprising:
a storage unit that stores a reservation management table in which a period for which the power consumption of the processes performed by the first and second non-volatile memories is greater than a first value is registered,
wherein, when the token is received, the first controller determines whether to cause the first non-volatile memory to perform the processes on the basis of the reservation management table,
when it is determined that the first non-volatile memory is caused to perform the processes, the first controller registers the period in the reservation management table and causes the first non-volatile memory to perform the processes, and
when it is determined that the first non-volatile memory is not caused to perform the processes, the first controller registers the period in a process which is finally performed in the reservation management table and performs the processes on the basis of the reservation management table.
15. The storage device according to claim 14,
wherein, at a start time of the period, a transition of the power consumption generated by the process of the first non-volatile memory while the process of the first non-volatile memory is performed is greater than the first value first, and
at an end time of the period, the transition of the power consumption generated by the process of the first non-volatile memory while the process of the first non-volatile memory is performed is finally less than the first value.
16. The storage device according to claim 14,
wherein, when the number of reservations of the processes performed by the first and second non-volatile semiconductor memories which overlap each other for the period is less than the number of tokens in the reservation management table, the first controller registers the period in the reservation management table and causes the first non-volatile memory to perform the processes.

The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.

1. An apparatus comprising:
a receiver configured to receive a routing protocol state change from a peer node;
a transmitter configured to send the routing protocol state change to a second controller,
wherein the receiver is further configured to receive a commitment to the routing protocol state change from the second controller; and
a committer configured to commit to the routing protocol state after receiving the commitment from the second controller,
wherein the transmitter is further configured to send the commitment to the peer node.
2. The apparatus of claim 1, wherein the receiver is further configured to send the routing protocol state change to a routing protocol after receiving the commitment from the second controller.
3. The apparatus of claim 1, wherein the transmitter is further configured to send the routing protocol state change to a routing protocol after receiving the routing protocol state change from the peer node.
4. The apparatus of claim 1, wherein the routing protocol state change comprises a border gateway protocol (BGP) state change, a routing internet protocol (RIP) state change, an open shortest path first protocol (OSPF) state change, or an intermediate system-to-intermediate system protocol (IS-IS) state change.
5. The apparatus of claim 1, further comprising:
a replicator configured to replicate selectively the received or generated routing protocol message to the second controller.
wherein the receiver is further configured to receive or generate a routing protocol message.
6. The apparatus of claim 1, further comprising:
a detector configured to detect a failure, wherein the second controller is configured to maintain the same routing protocol state changes in the apparatus prior to the failure.
7. An apparatus comprising:
a generator configured to generate a routing protocol state change to a peer node,
a transmitter configured to send the routing protocol state change to a second controller;
a receiver configured to receive a commitment to the routing protocol state change from the second controller; and
a committer configured to commit to the routing protocol state change after receiving the commitment from the second controller,
wherein the transmitter further configured to send the commitment to the peer node.
8. The apparatus of claim 7, wherein the transmitter is further configured to send the routing protocol state change to a routing protocol after receiving the commitment from the second controller.
9. The apparatus of claim 7, wherein the routing protocol state change comprises a border gateway protocol (BGP) state change, a routing internet protocol (RIP) state change, an open shortest path first protocol (OSPF) state change, or an intermediate system-to-intermediate system protocol (IS-IS) state change.
10. The apparatus of claim 7, further comprising:
a replicator configured to replicate selectively the received or generated routing protocol message to the second controller,
wherein the receiver is further configured to receive or generate a routing protocol message.
11. The apparatus of claim 7, further comprising:
a detector configured to detect a failure,
wherein the second controller is configured to maintain the same routing protocol state changes in the first controller prior to the failure.
12. An apparatus comprising:
a receiver configured to receive a routing protocol state change from a second controller;
a transmitter configured to send a commitment to the routing protocol state change to the second controller; and
a committer configured to commit to the routing protocol state change after sending the commitment to the second controller,
wherein the transmitter further configured to send the commitment to a peer node.
13. A method comprising:
receiving a routing protocol state change from a peer node by a first controller;
sending the routing protocol state change to a second controller;
receiving a commitment to the routing protocol state change by the first controller from the second controller;
committing to the routing protocol state change in the first controller; and
sending the commitment to the peer node by the first controller.
14. The method of claim 13, further comprising:
sending the routing protocol state change to a routing protocol after receiving the commitment from the second controller.
15. The method of claim 13, further comprising: sending the routing protocol state change to a routing protocol after receiving the routing protocol state change from the peer node.
16. A method comprising:
generating a routing protocol state change to a peer node by a first controller;
sending the routing protocol state change to a second controller;
receiving a commitment to the routing protocol state change by the first controller from the second controller;
committing to the routing protocol state change in the first controller; and
sending the commitment to the peer node by the first controller.
17. The method of claim 16, further comprising:
sending the routing protocol state change to a routing protocol after generating the commitment to the second controller.
18. An apparatus comprising:
receiving means for receiving a routing protocol state change from a peer node by a first controller;
sending means for sending the routing protocol state change to a second controller;
receiving means for receiving a commitment to the routing protocol state change by the from the second controller;
committing means for committing to the routing protocol state change in the first controller; and
sending means for sending the commitment to the peer node by the first controller.
19. An apparatus comprising:
generating means for generating a routing protocol state change to a peer node by a first controller;
sending means for sending the routing protocol state change to a second controller;
receiving means for receiving a commitment to the routing protocol state change by the first controller from the second controller;
committing means for committing to the routing protocol state change in the first controller; and
sending means for sending the commitment to the peer node by the first controller.