| 摘要 |
PURPOSE: A network processor architecture, scalable device driver service method and its related product is provided to offer a scalable processor and operating system independent of network processor services architecture and functional components for permitting customers or developers to customize and expand the available network services. CONSTITUTION: The architecture comprises a network device driver(301), a device driver(305), a physical transport service(341), a network processor(343), a network processor transport service(325), a control message service(329), a control message service(329), a control message formatting service(337), a customer definition service(307), and an interface manager service(309). The network processor device driver(301) includes external APIs(Application Programming Interface)(305), low level APIs(323) and physical transport interface(339). The device driver(305) is the software component that attaches a network processor hardware(343) to a software stack(300). The device driver(305) is responsible for being the interface between the network processor(343) and the software stack(300). The physical transport services(341) transport the frames to the network processor(343), provides a base send/receive API to transmit data and control frames to and from the network processor(343), and isolates the higher layer services from the physical connection of the network processor(343). The network processor(343) is connected to the device driver(301) and is a programmable, communications integrated circuits. The network processor(343) operates independent of and unaware of an architecture make-up of the device driver(301). The network processor transport service(325) is located above the physical transport service(341) and handles a specific network processor control and data encapsulation processing. The control message service(329) provides basic network processor initialization, code loading, event notification, debugger, diagnosis and software action service. The control message formatting service(337) is located in the lower level APIs(323) and is coupled to the external APIs(305), an OS(303), a software stack(300) and a network processor resource service(335).
|
