Limited duration supply for heuristic algorithms

Patent metadata

Field	Value
Publication number	US-11200296-B2
Application number	US-201715789557-A
Country	US
Kind code	B2
Filing date	Oct 20, 2017
Priority date	Oct 20, 2017
Publication date	Dec 14, 2021
Grant date	Dec 14, 2021

Abstract

Limited duration supply for heuristic algorithms is disclosed. A supply manager receives, from a first subsystem, a first request for a first supply. The supply manager determines that the first supply is not executing. The supply manager initiates the first supply, the first supply to return supply data upon request. The supply manager provides to the first subsystem a supply reference that refers to the first supply that allows the first subsystem to request the supply data directly from the first supply. The supply manager subsequently determines that no subsystem requires the first supply and disables the first supply.

First claim

What is claimed is:

1. A method comprising:
receiving, by a supply manager executing on a processor device, from a first subsystem, a first request for a first supply, wherein the first supply tracks supply data based on changes in a recommended solution state determined by a constraint satisfaction solver using the supply data;
determining, by the supply manager, that the first supply is not executing;
initiating the first supply, the first supply to return supply data upon request;
providing to the first subsystem a supply reference that refers to the first supply that allows the first subsystem to request the supply data directly from the first supply;
subsequently determining, by the supply manager, that no subsystem requires the first supply; and
disabling the first supply.

2. The method of claim 1 wherein the first subsystem implements a function to facilitate the determination by the constraint satisfaction solver of the recommended solution state from a plurality of solution states of a constraint problem, the constraint satisfaction solver executing in a plurality of stages, and wherein the constraint satisfaction solver continues to execute after the disabling of the first supply.

3. The method of claim 2 wherein the first request for the first supply includes a scope identifier that identifies a particular scope associated with a stage during which the first supply is needed, and wherein subsequently determining that no subsystem requires the first supply comprises subsequently determining, by the supply manager, that the constraint satisfaction solver has moved to a stage that has a scope that is different from the particular scope.

4. The method of claim 1 further comprising:
in response to receiving the first request for the first supply, incrementing a first supply counter;
subsequently receiving, from the first subsystem, an indication that the first subsystem no longer needs the first supply;
decrementing the first supply counter; and
wherein subsequently determining, by the supply manager, that no subsystem requires the first supply comprises determining, by the supply manager, that the first supply counter indicates that no subsystem is using the first supply.

5. The method of claim 1 further comprising:
receiving, from the first subsystem, an indication that the first subsystem no longer needs a second supply;
decrementing a second supply counter;
determining, by the supply manager, that the second supply counter indicates that another subsystem is continuing to use the second supply; and
not disabling the second supply to allow the second supply to continue to operate.

6. The method of claim 1 further comprising:
receiving, by the supply manager, from a second subsystem a request for a second supply that is different from the first supply, the request including a scope identifier that identifies a scope of a stage during which the second subsystem needs the second supply;
determining that the second supply exists;
determining that the second supply has an associated scope that is narrower than the scope of the stage during which the second subsystem needs the second supply;
setting the associated scope of the second supply to the scope of the stage during which the second subsystem needs the second supply; and
providing to the second subsystem a supply reference that refers to the second supply that allows the second subsystem to request data directly from the second supply.

7. The method of claim 1 further comprising:
receiving, by the supply manager, from a second subsystem a request for a second supply that is different from the first supply, the request including a scope identifier that identifies a scope of a stage during which the second subsystem needs the second supply;
determining that the second supply exists;
determining that the second supply has an associated scope that is wider than the scope of the stage during which the second subsystem needs the second supply; and
providing to the second subsystem a supply reference that refers to the second supply that allows the second subsystem to request data directly from the second supply.

8. The method of claim 1 further comprising:
receiving, by the supply manager, from the first subsystem, a request for a second supply that is different from the first supply;
determining, by the supply manager, that the second supply is not executing;
initiating the second supply; and
providing to the first subsystem a supply reference that refers to the second supply that allows the first subsystem to request the supply data directly from the second supply.

9. A computing device, comprising:
a memory;
a processor device coupled to the memory to:
receive, from a first subsystem, a first request for a first supply, wherein the first subsystem implements a function to facilitate a determination by a constraint satisfaction solver of a recommended solution state from a plurality of solution states of a constraint problem;
determine that the first supply is not executing;
initiate the first supply, the first supply to return supply data upon request;
provide to the first subsystem a supply reference that refers to the first supply that allows the first subsystem to request the supply data directly from the first supply;
subsequently, determine that no subsystem requires the first supply; and
disable the first supply.

10. The computing device of claim 9 the constraint satisfaction solver executing in a plurality of stages, and wherein the constraint satisfaction solver continues to execute after the disabling of the first supply.

11. The computing device of claim 10 wherein the first request for the first supply includes a scope identifier that identifies a particular scope associated with a stage during which the first supply is needed, and wherein to subsequently determine that no subsystem requires the first supply, the processor device is further to subsequently determine that the constraint satisfaction solver has moved to a stage that has a scope that is different from the particular scope.

12. The computing device of claim 9 wherein the processor device is further to:
in response to receiving the first request for the first supply, increment a first supply counter;
subsequently receive, from the first subsystem, an indication that the first subsystem no longer needs the first supply;
decrement the first supply counter; and
wherein to subsequently determine that no subsystem requires the first supply, the processor device is further to determine that the first supply counter indicates that no subsystem is using the first supply.

13. The computing device of claim 9 wherein the processor device is further to:
receive, from the first subsystem, an indication that the first subsystem no longer needs a second supply;
decrement a second supply counter;
determine that the second supply counter indicates that another subsystem is continuing to use the second supply; and
not disable the second supply to allow the second supply to continue to operate.

14. The computing device of claim 9 wherein the processor device is further to:
receive, from a second subsystem a request for a second supply that is different from the first supply, the request including a scope identifier that identifies a scope of a stage during which the second subsystem needs the second supply;
determine that the second supply exists;
determine that the second supply has an associated scope that is narrower than the scope of the stage during which the second subsystem needs the second supply;
set the associated scope of the second

Assignees

• Red Hat Inc

Inventors

• Petrovicky Lukas
• De Smet Geoffrey

Classifications

• G06N5/01 Primary

  Dynamic search techniques; Heuristics; Dynamic trees; Branch-and-bound · CPC title

• G06N5/013

  Automatic theorem proving · CPC title

• G06F8/22

  Procedural · CPC title

• G06F17/12 Primary

  Simultaneous equations {, e.g. systems of linear equations} · CPC title

• G06N3/126

  Evolutionary algorithms, e.g. genetic algorithms or genetic programming · CPC title