BACKGROUND OF THE INVENTION  
       [0001]     Immediate processing of data is very important when a device within a computing system runs a real time application. Such real time applications may involve the processing of video or audio. The device may require adequate bandwidth from one or more sources in order to effectively display images or reproduce audio. The device may require access to data stored in a memory of the computing system.  
         [0002]     Such computing systems may utilize a memory controller to access data stored in memory. The memory controller may employ a device called a memory arbiter that handles requests from one or more devices requiring access to data stored in memory. These devices may communicate to the memory using one or more data buses resident in the computing system.  
         [0003]     Often, a device running a real time application may not be able to receive data from main memory at a required rate. One or more other devices performing non-real time applications may consume bandwidth required by the device running the real time application. For example, a digital camcorder may require transmission of data from main memory at a sufficient rate in order to properly display video on a monitor. When other devices compete for memory resources, access to memory may not be provided to the most critical applications such as those which involve real time processing of data.  
         [0004]     Further limitations and disadvantages of conventional and traditional approaches will become apparent to one of skill in the art, through comparison of such systems with some aspects of the present invention as set forth in the remainder of the present application with reference to the drawings.  
       BRIEF SUMMARY OF THE INVENTION  
       [0005]     Aspects of the invention provide for a method and system to prioritize access to physical memory space in a main memory by way of categorizing memory requests transmitted by one or more devices communicating by a data bus. The memory requests are categorized as real time or non-real time. Real time memory requests have higher priority and are to be performed prior to non-real time memory requests.  
         [0006]     In one embodiment, the method comprises prioritizing access to memory by a bus compliant device. The method comprises receiving a memory request from a device through a data bus and comparing one or more addresses of the memory request to a range of memory addresses defined in hardware.  
         [0007]     In one embodiment, the system for accessing memory space for use by one or more devices comprises one or more device drivers, one or more bus drivers, and a memory request comparator. The one or more device drivers and the one or more bus drivers facilitate transmission of memory address ranges associated with one or more bus compliant devices.  
         [0008]     These and other advantages, aspects, and novel features of the present invention, as well as details of illustrated embodiments, thereof, will be more fully understood from the following description and drawings.  
     
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0009]      FIG. 1  illustrates a block diagram of a memory controller system in which memory requests transmitted by buses are prioritized based on whether the memory request relates to a real time application or a non-real time application, in accordance with an embodiment of the invention.  
         [0010]      FIG. 2  is a block diagram of a subsystem of the embodiment illustrated in  FIG. 1  that performs prioritization of memory requests transmitted by a data bus, in accordance with an embodiment of the invention.  
         [0011]      FIG. 3  is a block diagram of a memory request comparator in accordance with an embodiment of the invention.  
     
    
     DETAILED DESCRIPTION OF THE INVENTION  
       [0012]     Aspects of the present invention may be found in a system and method to prioritize access to memory by way of categorizing memory requests transmitted by one or more bus compliant devices in a computing system. The memory may comprise physical memory such as random access memory. In general, the memory requests may be requests generated by one or more bus compliant devices or other peripheral devices used to access the memory. The memory requests generated by the bus compliant devices are categorized as either a memory request associated with a real time application or a memory request associated with a non-real time application. A real time memory request is given a higher priority for allocating physical memory compared to that of a non-real time memory request. As a result, the memory request may be prioritized as a high priority memory request or a low priority memory request based on whether the memory request generated by the bus compliant device is associated with a real time application or a non-real time application.  
         [0013]      FIG. 1  illustrates a block diagram of a memory controller system  104  in which memory requests generated from buses  132 ,  136  are prioritized based on whether the memory request relates to a real time application or a non-real time application, in accordance with an embodiment of the invention. As shown the memory controller system  104  may interface with a number of different functional entities. In this exemplary embodiment, the memory controller system  104  interfaces with a first data bus  132 , a second data bus  136 , an MPEG engine  120 , a processor  124 , and a DMA engine  128 . The first data bus  132 , second data bus  136 , MPEG engine  120 , processor  124 , and DMA engine  128  may each generate memory requests to the memory controller system  104 . The memory controller system  104  comprises a memory arbiter  116 , a first memory request comparator  108 , and a second memory request comparator  112 . The memory arbiter  116  examines the one or more requests to determine the order of execution of received memory requests. The memory request comparators  108 ,  112  receive bus memory requests from their respective buses. The bus memory requests may be categorized as a real time request or a non-real time request based on the type of bus memory request received by the memory request comparators  108 ,  112 . The memory request comparators  108 ,  112  process these bus memory requests to generate a prioritized sequence of memory requests to the memory arbiter  116 . The memory arbiter  116  categorizes these bus requests along with any other requests from other functional entities such as the exemplary MPEG engine  120 , processor  124 , or DMA engine  128 , such that the main memory in a computing system is accessed in order of priority.  
         [0014]     In one embodiment, the exemplary first data bus  132  or second data bus  136  of  FIG. 1  may comprise a PCI, USB, ISA, EISA, or VESA data bus. It is contemplated that the first and second data buses  132 ,  136  may comprise any type of data bus.  
         [0015]      FIG. 2  is a block diagram of a subsystem of the embodiment illustrated in  FIG. 1  that performs prioritization of memory requests transmitted through a data bus (i.e., Bus  1  of  FIG. 1 ), in accordance with an embodiment of the invention. The subsystem comprises a memory request comparator  204 , a data bus  208 , and a number of bus compliant devices (devices capable of communicating through a data bus)  212 ,  216 ,  220  communicatively coupled to the data bus  208 . The memory request comparator  204  receives a bus memory request signal from the bus  208  based on memory requests made by the devices  212 ,  216 ,  220 . The number of devices may comprise a total of N devices, each capable of generating a memory request. In one embodiment N = 32 . As shown in  FIG. 2 , there may be a total of N devices communicating to a memory request comparator  204  by way of the bus  208 . As illustrated, device # 1   212  may generate a device # 1  memory request, device # 2  may generate a device # 2  memory request, while device #N  220  may generate a device #N memory request. It is contemplated that each of these devices utilizes software such as a suitable device driver and/or bus driver to perform such memory requests. Each device driver may specify a range of memory addresses associated with the memory request. The range of memory addresses may be used to determine whether the request to access memory is associated with a real time or a non-real time memory requirement of the device.  
         [0016]     In one embodiment, a device driver and/or bus driver initially specifies a range of addresses that define a “real time memory window” implemented in the memory request comparator  204 . The “real time window” within the memory request comparator  204  represents a portion of physical memory. It is contemplated that virtual memory used by an operating system may be mapped to corresponding physical memory (i.e., random access memory) by way of a callable system function provided by the operating system.  
         [0017]     In one embodiment, each (bus compliant) device  212 ,  216 ,  220  that requires real time access to memory will program or configure the memory request comparator  204  with a range of addresses that are used during real time applications. These range of memory addresses are termed a “real time memory window”. It is contemplated that one or more device or bus drivers from such devices may be utilized to program, implement, or configure “real time memory windows” into the memory request comparator  204 .  
         [0018]     When a memory access request is associated with addresses within a “real time memory window”, the memory access request is appropriately categorized by the memory request comparator  204  as a high priority memory request. Otherwise, the memory request is categorized as a low priority memory request. The low priority memory request may be termed a round robin type of memory request, in which these requests are performed in order of occurrence of all low priority requests. Use of this technique allows the memory request comparator  204  to analyze the address space generated by a memory request and appropriately determine whether the request is associated with a real time application or a non-real time application. The memory request may in turn allocate a certain region of physical memory for use by the device. The memory request comparator  204  may transmit a first control signal to the memory arbiter when the memory request corresponds to a high priority request. Otherwise, the memory request comparator  204  may transmit a second control signal to indicate a low priority request. In one embodiment, the second control signal indicates a round robin request. It is contemplated that the device and/or bus drivers will initiate a data transfer between memory and the device by way of the DMA engine shown in  FIG. 1 .  
         [0019]     The memory request comparator  204  comprises a circuitry such as logic gates and registers such that memory addresses of a memory access request received from a device may be compared to one or more “real time memory windows” defined by the memory request comparator  204 . The memory request comparator  204  is configured with a “real time memory window” for each bus compliant device that performs a real time application. It is contemplated that a device&#39;s “real time memory window” is established in the memory request comparator  204  at the time the corresponding device is powered up. The real time functionality of a device may determine whether a “real time memory window” is implemented within the memory request comparator  204 .  
         [0020]     In one embodiment, a “real time memory window” is represented by a range of addresses that are fully defined by two values (termed boundary values hereinafter) stored in a pair of n-bit registers. The two boundary values correspond to the endpoints of the range of addresses. Each n-bit register of the pair of n-bit registers stores a value represented by one n-bit word. In one embodiment, n corresponds to 32 bits while in another embodiment, n corresponds to 64 bits. These boundary values configure one or more “real time memory windows” using one or more device drivers of each of the N devices described in  FIG. 2 . In one embodiment, the two boundary values are provided to a memory request comparator  204  by way of one or more device drivers or bus drivers.  
         [0021]     When a device running a real time application or function requires access to memory, the corresponding device and/or bus drivers generate physical memory addresses that are located within the device&#39;s “real time memory window”. The memory request comparator  204  may act as a comparator used to compare or verify addresses transmitted by a device and/or bus driver to a range of addresses defined by its “real time memory window”. If the addresses fall within the “real time memory window”, the memory request comparator  204  sends an appropriate control signal (i.e., to a memory arbiter) indicating that the memory request constitutes a real time request.  
         [0022]      FIG. 3  is a block diagram of a memory request comparator  304  in accordance with an embodiment of the invention. The memory request comparator  304  comprises a number of “real time memory windows”  308 ,  312 ,  316 . Each “real time memory window”  308 ,  312 ,  316  represents either virtual or physical memory space required by a device that performs a real time application. The mapping or translation may be performed by way of a system function invoked by the operating system. As shown, real time memory window # 1   308  corresponds to a device # 1 , real time memory window # 2   312  corresponds to a device # 2 , while real time memory window #N  316  corresponds to the Nth device. When a bus memory request generated by a device is associated with addresses that are contained within a “real time memory window”, as determined by a memory request comparator  304 , a high priority (real time) request signal may be transmitted to a memory arbiter of a memory controller system. Otherwise, a low priority request signal, such as a round robin type of request may be transmitted to the memory arbiter. Each bus compliant device capable of running a real time application may implement a “real time memory window” within the memory request comparator  304 .  
         [0023]     The memory arbiter executes memory requests based on order of priority. It is contemplated that the memory arbiter employs a priority system that incorporates the high/low priority request signals generated by each “real time memory window” of each memory request comparator, in order to effectively process memory access requests from all types of devices.  
         [0024]     While the invention has been described with reference to certain embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted without departing from the scope of the invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the invention without departing from its scope. Therefore, it is intended that the invention not be limited to the particular embodiment disclosed, but that the invention will include all embodiments falling within the scope of the appended claims.
One or more methods and systems of prioritizing access of physical memory space to bus compliant devices in a computing device is presented. Prioritization is based on real time or non-real time device functionality. In one embodiment, the method of accessing physical memory space for use by a bus compliant device comprises receiving a memory request from the device through a data bus. In addition, the method comprises comparing addresses of the memory request to a range of memory addresses stored in a memory request comparator. In one embodiment, the system for prioritizing the access of physical memory space in response to memory requests comprises one or more device and/or bus drivers, and a memory request comparator. The one or more device and/or bus drivers facilitates implementation of address ranges within said memory request comparator for one or more bus compliant devices.