Network controller for obtaining a plurality of network port identifiers in response to load-store transactions from a corresponding plurality of operating system domains within a load-store architecture
First Claim
1. A controller shareable by a plurality of operating system domains (OSDs) for communication on a network, comprising:
- a port, for coupling to the network, configured to transceive packets with the network for each of the plurality of OSDs; and
a plurality of replicated programming interfaces, coupled to said port, each configured to receive from a respective one of the plurality of OSDs a respective request to obtain a port ID for said port from the network, wherein each said respective request comprises one or more load-store transactions, wherein the shared controller obtains from the network a distinct port ID for said respective one of the plurality of OSDs in response to each said respective request, where a respective one of said plurality of replicated programming interfaces is mapped into a location in a system load-store memory map of said respective one of the plurality of OSDs, wherein each of said plurality of replicated programming interfaces is mappable by said respective one of the plurality of OSDs into said location in said system load-store memory map, wherein said location may be distinct in each said system load-store memory map.
6 Assignments
0 Petitions
Accused Products
Abstract
A controller shareable by a plurality of operating system domains (OSDs) for communication on a network is disclosed. The controller includes a port for coupling to the network. The port transceives packets with the network for each of the plurality of OSDs. The controller also includes a plurality of replicated programming interfaces that each receive from a respective one of the plurality of OSDs a request to obtain a port ID for the port from the network. The controller obtains from the network a distinct port ID for each of the plurality of OSDs in response to the respective request. The request comprises one or more load-store transactions. In one embodiment, the controller is a shared Fiber Channel controller.
-
Citations
21 Claims
-
1. A controller shareable by a plurality of operating system domains (OSDs) for communication on a network, comprising:
-
a port, for coupling to the network, configured to transceive packets with the network for each of the plurality of OSDs; and a plurality of replicated programming interfaces, coupled to said port, each configured to receive from a respective one of the plurality of OSDs a respective request to obtain a port ID for said port from the network, wherein each said respective request comprises one or more load-store transactions, wherein the shared controller obtains from the network a distinct port ID for said respective one of the plurality of OSDs in response to each said respective request, where a respective one of said plurality of replicated programming interfaces is mapped into a location in a system load-store memory map of said respective one of the plurality of OSDs, wherein each of said plurality of replicated programming interfaces is mappable by said respective one of the plurality of OSDs into said location in said system load-store memory map, wherein said location may be distinct in each said system load-store memory map. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12)
-
-
13. A method for sharing a controller by a plurality of operating system domains (OSDs) for communication on a network, the controller having a ort for coupling to the network, configured to transceive packets with the network for each of the plurality of OSDs, and a plurality of replicated programming interfaces, the method comprising:
-
receiving at each of the plurality of replicated programming interfaces from a respective one of the plurality of OSDs a respective request to obtain a port ID for said port from the network, wherein each said respective request comprises one or more load-store transactions; obtaining from the network a distinct port ID for each of the plurality of OSDs, in response to said receiving each of said respective requests and mapping a respective one of said plurality of replicated programming interfaces into a location in a system load-store memory map of said respective one of the plurality of OSDs, wherein each of said plurality of replicated programming interfaces is mappable by said respective one of the plurality of OSDs into said location in said system load-store memory map, wherein said location may be distinct in each said system load-store memory map. - View Dependent Claims (14, 15, 16, 17, 18, 19)
-
-
20. A blade server environment comprising:
-
a plurality of blade servers; a shared switch for coupling to the plurality of blade servers, and for providing communication between the plurality of blade servers and a downstream endpoint, the downstream endpoint comprising a controller shareable by the plurality of blade servers for communication on a network, said shared controller comprising; a port, for coupling to the network, configured to transceive packets with the network for each of the plurality of blades; and a plurality of replicated programming interfaces, coupled to said port, each configured to receive from a respective one of the plurality of blade servers a respective request to obtain a port ID for said port from the network, wherein each said respective request comprises one or more load-store transactions, wherein the shared controller obtains from the network a distinct port ID for said respective one of the plurality of blade servers in response to each said respective request, wherein a respective one of said plurality of replicated programming interfaces is mapped into a location in a system load-store memory map of sad respective one of the plurality of blade servers, wherein each of said plurality of. - View Dependent Claims (21)
-
Specification