Dynamic storage resources

• US 8,706,900 B2
• Filed: 07/10/2008
• Issued: 04/22/2014
• Est. Priority Date: 07/10/2008
• Status: Active Grant

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Carver, David C., Gerovac, Branko J.
• Primary Examiner(s): Tiv, Backhean
• Application Number:
  US12/170,787
• Publication Number:
  US 20100011145A1
• Time in Patent Office: 2,112 Days
• Field of Search: 709/203, 709/224, 709/227, 709/228
• US Class Current: 709/234
• CPC Class Codes: H04L 67/5682 Policies or rules for updating, deleting or replacing the stored data

Abstract

A storage server in a distributed content storage and access system provides a mechanism for dynamically establishing storage resources, such as buffers, with specified semantic models. For example, the semantic models support distributed control of single buffering and double buffering during a content transfer that makes use of the buffer for intermediate storage. In some examples, a method includes examining characteristics associated with a desired transfer of data, such as a unit of content, and then selecting characteristics of a first storage resource based on results of the examining. The desired transfer of the data is then affected to use the first storage resource element.

Claims

1. A method comprising:

examining, by one or more network devices, characteristics associated with a transfer of data;

selecting, based on the examining and by the one or more network devices, a set of characteristics of a write buffer that buffers requests, associated with the data, during the transfer,

the set of characteristics including a plurality of rules regarding how the write buffer prioritizes read requests, that are associated with the transfer, with respect to write requests, that are associated with the transfer, the plurality of rules causing the write buffer to;

enter an empty state upon creation of the write buffer, in which the write buffer waits for a write request and denies all read requests received while waiting for the write request,

enter a write state upon receiving a write request while the write buffer is in the empty state, in which the write buffer handles write requests, and

enter a read state when a read request is received while the write buffer is in the write state, in which the write buffer handles all received read requests and queues incoming write requests; and

providing, by the one or more network devices, the selected set of characteristics to one or more devices that control the write buffer.

2. The method of claim 1, where, when examining the characteristics associated with the transfer, the method comprises:

examining characteristics of one or more units of the data.

3. The method of claim 1, where, when examining the characteristics associated with the transfer, the method comprises:

examining at least one of;

characteristics of one or more units of the data,

desired communication characteristics of the transfer,

a location of a source, or

a destination of the transfer.

4. The method of claim 1, where, when selecting the set of characteristics, the method comprises:

selecting a set of semantic constraints for the write buffer.

5. The method of claim 1, further comprising:

selecting a size of the write buffer based on the characteristics associated with the transfer.

6. The method of claim 1, further comprising:

passing data from a source of the transfer to the write buffer; and

passing data from the write buffer to a destination of the transfer.

7. The method of claim 1, further comprising:

determining whether the write buffer, that matches the selected set of characteristics, exists; and

requesting formation of the write buffer according to the selected characteristics when the write buffer does not exist.

8. The method of claim 1, where the plurality of rules further cause the write buffer to:

re-enter the write state upon receiving a write request while the write buffer is in the read state.

9. A method comprising:

receiving, by one or more network devices, a selection of a write buffer according to a selection of a semantic model associated with the write buffer,

the semantic model including a plurality of rules regarding how the write buffer prioritizes read requests, that are associated with a transfer of data, with respect to write requests, that are associated with the transfer of data, the plurality of rules causing the write buffer to;

enter an empty state upon creation of the write buffer, in which the write buffer waits for a write request and denies all read requests received while waiting for the write request,

enter a write state upon receiving a write request while the write buffer is in the empty state, in which the write buffer handles write requests, and

enter a read state when a read request is received while the write buffer is in the write state, in which the write buffer handles all received read requests and queues incoming write requests; and

forming, by the one or more network devices, the write buffer based on the plurality of rules;

receiving, by the one or more network devices, instructions to transfer the data using the formed write buffer.

10. The method of claim 9, further comprising:

providing an address for the formed write buffer.

11. The method of claim 10, where, when receiving the instructions to affect the transfer, the method comprises:

receiving instructions specifying the address of the formed write buffer.

12. The method of claim 9, where, when forming the write buffer, the method comprises:

forming a buffer storage element according to the selection of the semantic model.

13. The method of claim 9, where the plurality of rules further cause the write buffer to:

re-enter the write state when all read requests are handled.

14. A non-transitory computer-readable medium storing instructions the instructions comprising:

one or more instructions which, when executed by at least one processor, cause the at least one processor to;

examine characteristics associated with a transfer of data;

select, based on the examining, a set of characteristics of a write buffer that buffers requests, associated with the data, during the transfer,

the set of characteristics including a plurality of rules regarding how the write buffer prioritizes read requests, that are associated with the transfer, with respect to write requests, that are associated with the transfer, the plurality of rules causing the write buffer to;

enter an empty state upon creation of the write buffer, in which the write buffer waits for a write request and denies all read requests received while waiting for the write request,

enter a write state upon receiving a write request while the write buffer is in the empty state, in which the write buffer handles write requests, and

enter a read state when no write requests remain to be handled and when at least one read request is queued, in which the write buffer handles queued read requests and queues read and write requests received while handling queued read requests; and

provide the selected set of characteristics to one or more devices that control the write buffer.

15. The non-transitory computer-readable medium of claim 14, where the one or more instructions to examine the characteristics associated with the transfer comprise:

one or more instructions to examine characteristics of one or more units of the data.

16. The non-transitory computer-readable medium of claim 14, where the one or more instructions to examine the characteristics associated with the transfer examine at least one of:

characteristics of one or more units of the data,

desired communication characteristics of the transfer,

a location of a source, or

a destination of the transfer.

17. The non-transitory computer-readable medium of claim 14, where the one or more instructions to select the set of characteristics comprise:

one or more instructions to select a set of semantic constraints for the write buffer.

18. The non-transitory computer-readable medium of claim 14, where the plurality of rules further cause the write buffer to:

re-enter the write state when the write buffer is in the read state and no more read requests remain to be handled.