Classifications

• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F9/00—Arrangements for program control, e.g. control units
  • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
  • G06F9/46—Multiprogramming arrangements
  • G06F9/48—Program initiating; Program switching, e.g. by interrupt
  • G06F9/4806—Task transfer initiation or dispatching
  • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
  • G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F9/00—Arrangements for program control, e.g. control units
  • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
  • G06F9/46—Multiprogramming arrangements
  • G06F9/48—Program initiating; Program switching, e.g. by interrupt
  • G06F9/4806—Task transfer initiation or dispatching
  • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
  • G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F2209/00—Indexing scheme relating to G06F9/00
  • G06F2209/48—Indexing scheme relating to G06F9/48
  • G06F2209/485—Resource constraint

Definitions

• Provisional Patent Application Serial No. 60/ 161 ,206 entitled “Method For Implementing Scheduling Mechanisms By Utilizing Resource Characterizations," filed on October 21 , 1999, and to co-pending U.S. Provisional Patent Application Serial No. 06/ 160,991, entitled “Method For Quantifying Available System Resources Associated With A Hardware
• This invention relates generally to techniques for implementing electronic devices, and relates more particularly to a method for quantifying available system resources in an electronic device.
• An electronic device in an electronic network may advantageously communicate with other electronic devices in the network to share resources to thereby substantially increase the capabilities and versatility of individual devices in the electronic network.
• an electronic network may be implemented in a home environment to enable flexible and beneficial sharing of data and device resources between various consumer electronic devices, such as personal computers, digital video disc (DVD) devices, digital set-top boxes for digital broadcasting, enhanced television sets, and audio reproduction systems.
• Network size is also a factor that affects the management of resources in an electronic network.
• Communications in an electronic network typically become more complex as the number of individual devices or nodes increases.
• a local software module on A local device may need to communicate with various remote software elements on remote devices across the electronic network.
• successfully managing resources of a substantial number of electronic devices across a network may provide significant benefits to a system user.
• enhanced device capability to perform various advanced processes may provide additional benefits to a system user, but may also place increased demands on the control and management of an electronic device.
• an enhanced electronic device that effectively accesses, processes, and displays digital television programming may benefit from efficient use of resources because of the large amount and complexity of the digital data involved. Due to growing demands on system resources and substantially increasing data magnitudes, it is apparent that developing new and effective methods for managing resources is a matter of importance for the related electronic technologies. Therefore, for all the foregoing reasons, implementing effective methods for utilizing resources remains a significant consideration for designers, manufacturers, and users of contemporary electronic devices.
• a method for quantifying available system resources in an electronic device.
• device software preferably generates an isochronous process request to a cantaloupe manager that functions as a resource allocation manager for the electronic device.
• the cantaloupe manager preferably accesses resource usages or resource requirements that are listed in one or more resource characterizations known herein as "cantaloupes".
• the resource usages in an accessed cantaloupe preferably correspond to the foregoing isochronous process that was initially requested by the device software.
• the resource usages are preferably encoded in a native format that may be directly utilized by certain components of the electronic device without translation or conversion.
• the cantaloupe manager then may provide the hardware resource usage values from the cantaloupe to a request register as part of a resource allocation request.
• the resource allocator may then process each individual hardware resource usage value from the cantaloupe by comparing the each resource usage value with one or more corresponding currently-available resource values for the associated resource(s).
• the resource allocator may then preferably provide a corresponding allocation result to the cantaloupe manager via a status register.
• the cantaloupe manager preferably authorizes the device software to instantiate the requested process through a picokernel module. However, if sufficient currently-available resources are not present for optimal execution of the requested isochronous process, then the cantaloupe manager preferably generates a request-fail signal to the device software to thereby deny the request to instantiate the isochronous process. In this manner, the present invention advantageously pre-allocates sufficient guaranteed resources for a given isochronous process, prior to instantiation, to thereby guarantee successful and deterministic performance of the requested isochronous process. The present invention therefore provides an effective method for quantifying available system resources in an electronic device.
• FIG. 1 is a block diagram for one embodiment of an electronic network, in accordance with the present invention.
• FIG. 2 is a block diagram for one embodiment of an exemplary device of FIG. 1 , in accordance with the present invention
• FIG. 3 is a diagram for one embodiment of the memory of FIG. 2, in accordance with the present invention.
• FIG. 4 is a block diagram for one embodiment of a cantaloupe, in accordance with the present invention.
• FIG. 5 is a block diagram for one embodiment of a resource allocation request, in accordance with the present invention.
• FIG. 6 is a block diagram that illustrates the quantifying of available system resources, in accordance with one embodiment of the present invention.
• FIG. 7 is a flowchart of method steps for performing a resource allocation procedure, in accordance with one embodiment of the present invention.
• FIG. 8 is a flowchart of method steps for quantifying available system resources, in accordance with one embodiment of the present invention.
• the present invention relates to an improvement in electronic devices.
• the following description is presented to enable one of ordinary skill in the art to make and use the invention and is provided in the context of a patent application and its requirements.
• Various modifications to the preferred embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments.
• the present invention is not intended to be limited to the embodiment shown, but is to be accorded the widest scope consistent with the principles and features described herein.
• the present invention comprises a method for quantifying resources in an electronic device, and includes a resource characterization with resource requirements for a requested process which are encoded in a native format that is directly compatible with certain components in the electronic device.
• An allocation manager may then create a resource allocation request based on the resource requirements, and then provide the resource allocation request to a resource allocator that responsively may compare the resource requirements for the requested process to the currently-available device resources to generate an allocation result.
• the allocation manager may then authorize or deny the requested process depending upon whether the currently-available resources are sufficient to adequately service the resource requirements of the requested process.
• network 110 preferably comprises, but is not limited to, a number of electronic devices 112 (device A 1 12(a), device B 1 12(b), root device 114, device C 1 12(c), device D 1 12(d), and device E 1 12(e)).
• electronic network 1 10 may readily be configured to include various other devices or components that function in addition to, or instead of, those discussed in conjunction with the FIG. 1 embodiment.
• network 1 10 may readily be connected and configured in any other appropriate and suitable manner.
• devices 1 12 of network 1 10 may be implemented as any type of electronic device, including, but not limited to, personal computers, printers, digital video disc devices, television sets, audio systems, video cassette recorders, and set-top boxes for digital broadcasting.
• devices 1 12 preferably communicate with one another using a network bus 132.
• Network bus 132 preferably includes path 132(a), path 132(b), path 132(c), path 132(d), and path 132(e).
• device B 1 12(b) is coupled to device A 1 12(a) via path 132(a), and to root device 1 14 via path 132(b).
• root device 1 14 is coupled to device C 1 12(c) via path 132(c), and to device D 1 12(d) via path 132(d).
• device D 112(d) is coupled to device E 112(e) via path 132(e).
• network bus 132 is preferably implemented using an IEEE Std 1394 Standard for a High Performance Serial Bus, which is hereby incorporated by reference.
• network 1 10 may readily communicate and function using various other network interconnectivity methodologies which are equally within the scope of the present invention.
• each device in electronic network 110 may preferably communicate with any other device within network 110.
• device E 1 12(e) may communicate with device B 112(b) by transmitting transfer data via cable 132(e) to device D 112(d), which then may transmit the transfer data via cable 132(d) to root device 114.
• root device 114 then may transmit the transfer data to device B 112(b) via cable 132(b).
• root device 114 preferably provides a master cycle start signal to synchronize isochronous processes for devices 112 in network 110.
• any one of the network devices 112 may be designated as the root device or cycle master.
• Device 1 12 preferably includes, but is not limited to, a processor 212, an input/output (I/O) interface 214, a memory 216, a device bus 226, and a bus interface 220.
• processor 212, I/O interface 214, memory 216 and bus interface 220 preferably are each coupled to, and communicate via common device bus 226.
• processor 212 may be implemented as any appropriate multipurpose microprocessor device.
• Memory 216 may be implemented as one or more appropriate storage devices, including, but not limited to, read-only memory, random-access memory, and various types of non- volatile memory, such as floppy disc devices or hard disc devices.
• I/O interface 214 preferably may provide an interface for communications with various compatible sources and/ or destinations.
• bus interface 220 preferably provides an interface between device 112 and network 1 10. In the FIG. 2 embodiment, bus interface 220 preferably communicates with other devices 1 12 on network 110 via network bus 132. Bus interface 220 also preferably communicates with processor 212, I/O device 214, and memory 216 via a common device bus 226.
• device 1 12 preferably includes the capability to perform various tasks that involve isochronous data and isochronous processes.
• Isochronous data typically includes information that is time- sensitive, and therefore requires deterministic operations to guarantee delivery and processing of the isochronous data in a timely manner. For example, video data that is intended for immediate display must arrive at the appropriate destination in a timely manner in order to prevent jitter or breakup of the corresponding image during display.
• device 1 12 preferably performs isochronous and other types of processing in segments of time called "cycles".
• Scheduling of isochronous processes typically requires a finite time period that is sometimes referred to as "overhead". As the cycle time period is reduced, the overhead becomes a more significant factor because of the reduced amount of time remaining to perform the actual isochronous transfer.
• the cycle time period may be in the proximity of 125 microseconds, with a cycle frequency of approximately eight kilohertz.
• memory 216 preferably includes, but is not limited to, device software 312, picokernel 314, cantaloupe manager 316, cantaloupe(s) 318, and resource values 320.
• memory 216 may readily include various other components in addition to, or instead of, the components that are discussed in conjunction with the FIG. 3 embodiment.
• device software 312 includes software instructions that are preferably executed by processor 212 for performing various functions and operations by device 112. The particular nature and functionality of device software 312 preferably varies depending upon factors such as the type and purpose of the corresponding host device 112.
• picokernel 312 preferably controls and coordinates the scheduling of isochronous processes by utilizing an optimized process representation to reduce the cost or overhead of scheduling to a minimum.
• Cantaloupe manager 316 preferably includes an allocation manager that may utilize information from cantaloupe(s) 318 to determine whether a particular isochronous process may be instantiated on behalf of another entity, such as device software 312.
• Cantaloupe(s) 318 preferably comprise a resource characterization that includes one or more characterizations of hardware and/ or software resources necessary to meet performance criteria for a particular isochronous process.
• Cantaloupe(s) 318 are further discussed below in conjunction with FIGS. 4, 6, and 7.
• Resource values 320 preferably include any relevant information regarding current resource availability and allocations in device 112.
• resource values 320 may include one or more currently-available resource value(s), one or more currently-allocated resource value(s), and one or more total device resource value(s) for device 1 12.
• the available resource value(s) may initially be set to a value that is less than 100% of total device resource values (such as 75%) to thereby reserve resources necessary for non-isochronous processes or system tasks.
• cantaloupe 318 preferably includes a listing for a resource 1
• resources 412 may include any appropriate aspects of devices 1 12 or network 1 10 (FIG. 1).
• resource 412 may correspond to the bandwidth for a particular bus, such as device bus 226 or network bus 132.
• resource 412 may correspond to the processing capacity for a central processing device, such as processor 212 (FIG. 2), or to the capacity of a memory device, such as memory 216.
• cantaloupe 318 may readily be implemented to include various other configurations, and may also include various items and components that are different from those discussed in conjunction with the FIG. 4 embodiment.
• cantaloupe 318 is preferably associated with a particular time- sensitive isochronous or plesiochronous process on network 1 10.
• cantaloupe manager 316 may then advantageously reference cantaloupe 318 to determine the individual and total resources necessary for the associated process. Determining in advance whether sufficient system resources are available for successful operation of a given process ensures that the associated isochronous process is guaranteed sufficient resources for timely and deterministic performance. Providing sufficient resources becomes more significant as the cycle duration decreases and the cycle frequency increases.
• cantaloupe 318 preferably also includes a listing for a resource 1 usage (414(a)) through a listing for a resource N usage (414(c)).
• each of resource usages 414 preferably corresponds with a given resource 412 to characterize the amount of the given resource 412 required by the isochronous or plesiochronous process associated with cantaloupe 318.
• resource usages 414 may be implemented in any appropriate and compatible format for use by network 1 10, including a percentage value, or a native format that is directly compatible with certain other components.
• cantaloupe 318 may be implemented using only resource usages 414, with the corresponding resources 412 indirectly implied and understood during instantiation of process on network 1 10.
• cantaloupe 318 may also be utilized to characterize other resources, such as the total system resources, or the current available resources of device 112.
• cantaloupe 318 preferably includes an at least two-dimensional array of descriptive parameters.
• the first parameter preferably may be the type of resource being characterized, and the second parameter is the amount of required resource usage.
• a cantaloupe 318 may thus serve as a common descriptor to couple hardware and software scheduling mechanisms by describing resource requirements. For example, resource usage may be characterized and described as a ratio of the amount of usage per a given time period (including process scheduling overhead).
• FIG. 5 a diagram for one embodiment of a resource allocation request 510 is shown, in accordance with the present invention.
• resource allocation request 510 preferably includes a command identifier (command ID) 512, and one or more resource usage value(s) 414.
• resource allocation request 510 may include various elements or fields in addition to, or instead of, those discussed in conjunction with the FIG. 5 embodiment.
• cantaloupe manager 316 preferably transmits a series of resource allocation requests 510 to a resource 412, including certain hardware components, as further discussed below in conjunction with FIG. 6.
• command ID 512 preferably includes information regarding the functionality of resource request 510.
• command ID 512 may include a "test" command to request resource 412 to provide a test result in response to the resource allocation request 510.
• command ID 512 may include a "do" command to request resource 412 to actually allocate the corresponding resource 412 in response to the resource allocation request 510.
• command ID 512 may include an "undo" command to request resource 412 to deallocate the corresponding resource 412 in response to the resource allocation request 510.
• cantaloupe manager 316 preferably obtains the resource usage value 414 for resource allocation request 510 directly from a cantaloupe 318 (FIG. 4) corresponding to a requested isochronous process.
• resource usages 414 for resources are advantageously encoded in cantaloupe 318 in a format that is native to the corresponding resource 412.
• a resource usage value 414 for a resource 412 may simply be a number, such as the percentage of the total resource 412 that is required for an associated isochronous process.
• Cantaloupe manager 316 may thus transmit a resource usage value 414 to a corresponding resource 412 without the need to process or translate the resource usage value 414 into a format that is compatible with the resource 412.
• FIG. 6 a block diagram that illustrates the quantifying of available system resources is shown, in accordance with one embodiment of the present invention.
• system resources may readily be quantified in other manners by using various different hardware configurations, in accordance with the present invention.
• device software 312 initially generates an isochronous process request to cantaloupe manager 316 via path 618.
• the isochronous process request preferably requires the utilization of one or more hardware resources 412 or other types of resources 412.
• cantaloupe manager 316 preferably accesses corresponding resource usage values 414 in cantaloupe 318 via path 614.
• cantaloupe 318 preferably corresponds to the isochronous process that was initially requested by device software 312.
• the foregoing cantaloupe 318 preferably includes resource usage values 414 that are encoded in a format that is native to the corresponding hardware or other resources 412, as discussed above in conjunction with FIG. 5.
• Cantaloupe manager 316 then may sequentially or concurrently provide the resource usage values 414 from cantaloupe 318 to a request register 628 via path 620 as part of the resource allocation request 510 (FIG. 5).
• resource allocator 630 may then sequentially or concurrently compare each individual resource usage value 414 from cantaloupe 318 to one or more corresponding currently- available resources of the associated resource(s) 412.
• the one or more currently- available resources may preferably be determined by subtracting currently- allocated resource values from one or more total device resource values.
• resource allocator 630 is preferably implemented using a hardware configuration.
• resource allocator 630 may include an input device that provides a received resource usage value 414 to an accumulator device.
• the accumulator device may responsively add the received resource usage value 414 to a currently-allocated resource value for a particular resource 412.
• the accumulator thus generates a proposed allocated resource value for the associated resource value 412.
• a comparator device may then compare the proposed allocated resource value from the accumulator with a total device resource value for the particular resource 412 to determine whether a sufficient amount of the particular resource is available for the requested process.
• cantaloupe manager 316 preferably may utilize resource allocator 630 to evaluate each resource usage value 414 from cantaloupe 318. Resource allocator 630 then preferably provides an allocation result via path 624 to status register 632 to indicate whether sufficient additional resources are available for the requested isochronous process.
• resource allocator 630 may be implemented as a re-configurable allocation software module that is compatible with the semantics of cantaloupe 318.
• the allocation software module preferably may perform appropriate resource arithmetic to translate the non-native resource usages 414 for compatible use by the corresponding resource 414.
• Cantaloupe manager 316 may then access status register 632 via path
• cantaloupe manager 316 preferably authorizes device software 312 to schedule and instantiate the requested process through picokernel 314. However, if sufficient current resources 412 are not available for the requested isochronous process, then cantaloupe manager 316 preferably generates a request fail signal to device software 312 to deny authorization for instantiating the requested isochronous process. In this manner, the present invention advantageously pre-allocates sufficient resources for a given isochronous process, prior to instantiation, to thereby guarantee successful and deterministic performance of the isochronous process.
• FIG. 7 a flowchart of method steps for performing a resource allocation procedure is shown, in accordance with one embodiment of the present invention. In alternate embodiments, the FIG. 7 resource allocation procedure may readily be performed in various other manners and sequences, in accordance with the present invention.
• an entity such as device software 312 preferably generates a request for instantiation of an isochronous process.
• cantaloupe manager 316 preferably examines one or more cantaloupes 318 that correspond to the requested isochronous process.
• cantaloupe manager 316 preferably determines whether sufficient resources are currently available for performing the requested isochronous process.
• cantaloupe manager 316 may utilize any appropriate technique to determine whether sufficient resources are available for performing the requested process. One such technique is further discussed below in conjunction with the FIG. 8 embodiment, in accordance with the present invention.
• cantaloupe manager 316 preferably maintains one or more currently- available resource values 320 in memory 216 (FIG. 3) to quantitatively represent any currently unallocated resources.
• currently-available resource values may be expressed as percentages of total system resources, or as a finite resource amount. The present invention may then be utilized to compare the resources required for the requested process (obtained from cantaloupe(s) 318) and the currently- available resource value(s) to determine whether sufficient unallocated resources are available for utilization by the requested process.
• step 720 if cantaloupe manager 316 determines that sufficient resources are not available for performing the requested process, then, in step 724, cantaloupe manager 316 preferably denies the request for instantiation of the process, and the FIG. 7 method terminates. However, if cantaloupe manager 316 determines that sufficient resources are available for performing the requested process, then, in step 728, cantaloupe manager 316 preferably allocates the required resources, and grants the request for instantiation of the isochronous process.
• cantaloupe manager 316 preferably updates the currently- available resource value(s) in memory 216 to include those resources that were allocated in foregoing step 728 to service the requested isochronous process. For example, if the requested process requires twenty-five percent of system resources, then, cantaloupe manager 316 preferably may decrease the currently-available resources in memory 216 by twenty-five percent.
• picokernel 314 of device 1 12 preferably may instantiate and execute the requested isochronous process. The resources that are allocated for the isochronous process are therefore guaranteed to be available, and the isochronous process is thus assured of successful execution without degraded or non-optimal performance.
• the FIG. 7 process may readily be utilized to evaluate a series of requested isochronous processes.
• FIG. 8 a flowchart of method steps for quantifying available system resources is shown, in accordance with one embodiment of the present invention.
• the FIG. 8 method illustrates a technique for determining whether sufficient resources are available for a requested process (step 720 of FIG. 7).
• system resources may readily be quantified using sequences and procedures other than those discussed below in conjunction with the FIG. 8 embodiment.
• cantaloupe manager 316 preferably creates a resource allocation request 510 by referencing cantaloupe 318 to access resource usage values 414 that are encoded in a native format that is directly compatible with the corresponding resources 412 and resource allocator 630, as discussed above in conjunction with FIGS. 5 and 6.
• cantaloupe manager 316 may then provide the resource usage values 414 from cantaloupe 318 to a request register 628 as part of the resource allocation request 510.
• resource allocator 630 may then sequentially or concurrently process each individual resource usage value 414 from cantaloupe 318 by comparing each resource usage value 414 with one or more corresponding currently- available resource values for the associated hardware resource(s) 412.
• resource allocator 630 may preferably be implemented using a hardware configuration.
• resource allocator 630 may include an input device that provides a received resource usage value 414 to an accumulator device.
• the accumulator device may responsively add the received resource usage value 414 to a currently- allocated resource value for a particular resource 412. The accumulator thus generates a proposed allocated resource value for the associated resource value 412.
• a comparator device may then compare the proposed allocated resource value from the accumulator to a total device resource value for the particular resource 412 to determine whether sufficient resources are available for the requested process.
• resource allocator 630 then preferably may provide an allocation result to status register 632 to advantageously indicate whether sufficient resources are available for the requested isochronous process.

Landscapes

• Engineering & Computer Science (AREA)
• Software Systems (AREA)
• Theoretical Computer Science (AREA)
• Physics & Mathematics (AREA)
• General Engineering & Computer Science (AREA)
• General Physics & Mathematics (AREA)
• Small-Scale Networks (AREA)
• Multi Processors (AREA)
• Computer And Data Communications (AREA)

Applications Claiming Priority (7)

Publications (1)

Family

ID=27388548

Family Applications (1)

Country Status (4)

Families Citing this family (3)

Family Cites Families (4)

• 2000
  • 2000-10-18 WO PCT/US2000/041313 patent/WO2001029686A1/en not_active Application Discontinuation
  • 2000-10-18 JP JP2001532412A patent/JP2003515265A/ja not_active Withdrawn
  • 2000-10-18 EP EP00984570A patent/EP1224561A1/de not_active Withdrawn
  • 2000-10-18 AU AU21170/01A patent/AU2117001A/en not_active Abandoned

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events