Abstract:
In one embodiment, the present invention includes an apparatus having a central processing unit (CPU) to execute instructions, a hub coupled to the CPU, and multiple physical devices coupled to the hub. The physical devices may each correspond to a different network communication protocol, and may each include a physical unit to forward packets to the hub while the system is in a low power mode. The hub may remain enabled during the low power mode and may include media access control functionality for handling incoming packets of different physical devices. Other embodiments are described and claimed.

Description:
[0001]    This application is a continuation of U.S. patent application Ser. No. 11/729,064, filed Mar. 28, 2007 the content of which is hereby incorporated by reference. 
     
    
     BACKGROUND 
       [0002]    Today&#39;s computer systems include many different components and physical interconnects to interconnect a given platform to various devices. In systems for the digital office and home, these different physical interconnects may include in addition to Ethernet connections, various wireless connections such as a so-called Wi-Fi connection in accordance with an Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard such as an IEEE 802.11a/b/g standard, an ultra wideband (UWB) connection, a Bluetooth™ connection in accordance with a Bluetooth™ protocol, among many others. 
         [0003]    A major issue in today&#39;s systems is reducing the amount of power consumed. Accordingly, various low power modes are available in many systems. However, to be able to remain interconnected for communication with these various physical interconnects, oftentimes many dedicated components within a system are required to remain powered on, reducing the benefits of low power states. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0004]      FIG. 1  is a block diagram of a system in accordance with an embodiment of the present invention. 
           [0005]      FIG. 2  is a flow diagram of a method in accordance with an embodiment of the present invention. 
       
    
    
     DETAILED DESCRIPTION 
       [0006]    In various embodiments, a generic processing engine, such as may be present in a chipset of a system, may provide for performing certain protocol operations such as implemented in a media access control (MAC) unit to enable more of a given system to remain in a low power state, yet provide for connectivity to network packets received by the system. While the scope of the present invention is not limited in this regard, such a generic processing engine, which may be a general-purpose microprocessor, may be included in a chipset component such as a memory controller, input/output (I/O) controller or other such interface component. Note that this processing engine may be a generic application processor located in the chipset, with access to the different physical interfaces in the platform, which can then be used to provide network services across multiple physical interfaces. 
         [0007]    Referring now to  FIG. 1 , shown is a block diagram of a system in accordance with an embodiment of the present invention. As shown in  FIG. 1 , system  10  includes a processor  20 , which may be a microprocessor such as a multi-core processor. Processor  20  is coupled to a memory controller hub (MCH)  30  that includes a manageability engine (ME)  35 . ME  35  may be configured to handle MAC features for various physical interconnects of system  10  to enable greater low power operation of system  10 , while retaining network connectivity. 
         [0008]    Still referring to  FIG. 1 , MCH  30  is coupled to a memory  40 , which may be a dynamic random access memory (DRAM), e.g., a double data rate (DDR) memory. MCH  30  is further coupled to a graphics unit  50 , which may be a graphics adaptor that in turn is provided to a display. In turn, MCH  30  is coupled to an I/O controller hub (ICH)  60 . As shown, ICH  60  includes a MAC  65  such as a MAC unit of a gigabit Ethernet (GBE) network interface. In turn, ICH  60  is coupled to various physical interconnects, such as a wireless local area network (WLAN) adaptor  70 , which may be in accordance with a given IEEE 802.11 standard or another local wireless protocol. Furthermore, ICH  60  is coupled to a physical (PHY) adaptor  80 , which may be a network interconnect to an Ethernet network such as a GBE connection. ICH  60  is further coupled to a hard disk drive  90  and via a peripheral bus (e.g., a peripheral component interconnect (PCI) bus) to a PCI device  95 , which may be a desired adaptor card or so forth. Note while shown with this particular implementation in the embodiment of  FIG. 1 , other implementations are possible. For example, in some implementations processor  20  may further include the components of MCH  30  and graphics unit  50 , for example. 
         [0009]    In various embodiments, ME  35  can provide network service aliveness across the multiple disparate physical network interfaces shown in  FIG. 1 . To enable ME  35  to provide service aliveness in a low power mode, various MAC-like components may be implemented in ME  35 . For example, a generic port filter may be configured to execute on ME  35  such that the need for independent port filters for the various network devices shown in  FIG. 1  can be avoided. In various embodiments, ME  35  may include hardware, software, firmware or combinations thereof to handle port filtering and processing of incoming packets when other portions of system  10  are in a low power state. Note in some embodiments the port filtering may be performed by combinations of software and/or firmware that execute on generic hardware of ME  35 , allowing for a flexible framework for various usage scenarios. Furthermore, by handling packet detection response capabilities in ME  35 , the cost of the associated physical interconnects may be reduced, as port filtering capabilities among other packet detection processing can be moved from the components to ME  35 . To provide for a great deal of flexibility to both fine tune what interface source is maintained and how such services may be advertised on different interfaces, a configuration process may be performed in which a host (e.g., processor  20 ) may configure ME  35  to handle various packet types that may be associated with different network interfaces and the different applications, to be handled appropriately in a low power state. 
         [0010]    Referring now to  FIG. 2 , shown is a flow diagram of a method in accordance with an embodiment of the present invention. As shown in  FIG. 2 , method  100  may begin by receiving configuration and registration information regarding services available in a low power state (block  110 ). For example, in various implementations a processor may provide an ME with various information regarding different applications that are to possibly receive data while a system is in a low power state. The information may further correspond to given packet types, e.g., based on internet protocol (IP) address or so forth such as a port basis or in another manner, which may be used to handle incoming packets when in the low power mode. As shown in  FIG. 2 , such information may be stored in a non-volatile memory that is accessible by the ME (block  120 ). For example, in various embodiments a flash memory that may be present in a chipset in which ME is included, or another non-volatile memory to which it may have access can be used to store this information. Alternately, the information may be stored in a volatile memory where a host re-programs the memory every time before going to sleep. This information may be stored, for example, in a table that the ME can access when it receives an incoming packet during a low power mode. 
         [0011]    Referring still to  FIG. 2 , during operation it may be determined whether a low power mode is present (diamond  130 ). For example, a processor such as processor  20  of  FIG. 1  may send a message to ME  35  when it enters into a low power mode. If it is determined that the low power mode is present, next it may be determined whether an incoming packet is received at the ME from a given MAC unit in the system (diamond  140 ). If not, diamond  140  may loop back on itself. If an incoming packet is received, control passes to diamond  150  where it may be determined whether the packet corresponds to registered information (diamond  150 ). That is, it may be determined whether information associated with the packet, e.g., by way of port information, IP address information, packet type or so forth corresponds to data present in the non-volatile storage. If not, the packet may be dropped (block  160 ). 
         [0012]    If instead the packet corresponds to the information in the non-volatile memory, the ME may handle the packet according to the information that is stored in the memory (block  170 ). For example, depending on the information stored in the memory that corresponds to the packet, the packet may be sent to a predetermined location, a wakeup signal may be sent to a given component, a response packet may be sent, e.g., in the example of a heartbeat message sent from a remote source or so forth. For example, if an incoming packet is a Bluetooth™ packet, certain limitations may exist in handling a packet in a low power mode. For example, such services as video streaming may not be provided due to limited available bandwidth, while a similar packet advertised over Ethernet may be handled. While shown with the particular implementation in the embodiment of  FIG. 2 , the scope of the present invention is not limited in this regard. 
         [0013]    Embodiments may be implemented in code and may be stored on a storage medium having stored thereon instructions which can be used to program a system to perform the instructions. The storage medium may include, but is not limited to, any type of disk including floppy disks, optical disks, compact disk read-only memories (CD-ROMs), compact disk rewritables (CD-RWs), and magneto-optical disks, semiconductor devices such as read-only memories (ROMs), random access memories (RAMs) such as dynamic random access memories (DRAMs), static random access memories (SRAMs), erasable programmable read-only memories (EPROMs), flash memories, electrically erasable programmable read-only memories (EEPROMs), magnetic or optical cards, or any other type of media suitable for storing electronic instructions. 
         [0014]    While the present invention has been described with respect to a limited number of embodiments, those skilled in the art will appreciate numerous modifications and variations therefrom. It is intended that the appended claims cover all such modifications and variations as fall within the true spirit and scope of this present invention.