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

• US 7,502,370 B2
• Filed: 01/27/2005
• Issued: 03/10/2009
• Est. Priority Date: 01/21/2003
• Status: Active Grant

• Current Assignee: Mellanox Technologies Limited (NVIDIA Corporation)
• Original Assignee: NextIO Incorporated
• Inventors: Pettey, Christopher J.
• Primary Examiner(s): Chan, Wing F
• Assistant Examiner(s): CAMPBELL, MATTHEW T
• Application Number:
  US11/045,869
• Publication Number:
  US 20050157754A1
• Time in Patent Office: 1,503 Days
• Field of Search: 370/355, 370/389, 370/469, 711/1, 711/200, 710/3, 710/8, 710/9, 710/10, 710/62, 710/305, 710/306
• US Class Current: 370/389
• CPC Class Codes: G06F 3/00 Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
• CPC Class Codes: H04J 3/12 Arrangements providing for calling or supervisory signals
• CPC Class Codes: H04J 3/16 in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted H04J3/17, H04J3/24 take precedence
• CPC Class Codes: H04J 3/22 in which the sources have different rates or codes simultaneous speech and digital data or video transmission H04M11/06; see provisional also H04J3/16
• CPC Class Codes: H04N 21/443 OS processes, e.g. booting an STB, implementing a Java virtual machine in an STB or power management in an STB
• CPC Class Codes: H04N 5/50 Tuning indicators; Automatic tuning control

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.

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.

2. The shareable controller as recited in claim 1, wherein said port transceives said packets with said network using said distinct port IDs obtained for each of the plurality of OSDs.

3. The shareable controller as recited in claim 2, wherein said port transceives said packets with said network using said distinct port IDs obtained for each of the plurality of OSDs in response to I/O operation requests programmed into said respective ones of said plurality of programming interfaces.

4. The shareable controller as recited in claim 1, wherein said request comprises a notification that said respective OSD has become active.

5. The shareable controller as recited in claim 1, wherein said load-store transactions comprise PCI Express transactions.

6. The shareable controller as recited in claim 1, wherein the shareable controller comprises a shareable Fibre Channel (FC) controller.

7. The shareable controller as recited in claim 6, wherein said port comprises a FC port for coupling to a FC network.

8. The shareable controller as recited in claim 7, wherein said packets comprise FC frames.

9. The shareable controller as recited in claim 8, wherein said distinct port IDs comprise distinct FC Nx_Port_IDs.

10. The shareable controller as recited in claim 9, wherein said FC port is configurable as a FC NL_Port for linking to a FC arbitrated loop.

11. The shareable controller as recited in claim 9, wherein said FC port comprises a FC N_Port for linking to a FC F_Port supporting a FC Multiple N_port_ID Assignment capability.

12. The shareable controller as recited in claim 11, wherein the shared controller obtaining from said network a distinct port ID comprises the shared controller obtaining from said FC F_Port a respective FC N_Port identifier for the OSD that requested the shareable controller to obtain a port ID.

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.

14. The method as recited in claim 13, further comprising:

transceiving said packets with said network using said distinct port IDs obtained for each of the plurality of OSDs.

15. The method as recited in claim 13, wherein said load-store transactions comprise PCI Express transactions.

16. The method as recited in claim 13, wherein the shareable controller comprises a shareable Fibre Channel (FC) controller, wherein said port comprises a FC port for coupling to a FC network, wherein said packets comprise FC frames, wherein said distinct port IDs comprise distinct FC Nx_Port_IDs.

17. The method as recited in claim 16, wherein said FC port comprises a FC N_Port for linking to a FC F_Port supporting a FC Multiple N_Port_ID Assignment capability, wherein said obtaining from said network a distinct port ID comprises obtaining from said FC F_Port a respective FC N_Port identifier for the OSD that requested the shareable controller to obtain a port ID.

18. The method as recited in claim 13, further comprising:

determining that one of the plurality of OSDs has been reset; and

disclaiming the distinct port ID for the one of the plurality of OSDs that has been reset, in response to said determining.

19. The method as recited in claim 18, wherein said disclaiming the distinct port ID for the one of the plurality of OSDs that has been reset comprises logging out of a network to which the controller is linked for the distinct port ID for the one of the plurality of OSDs that has been reset.

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.

21. The blade server environment as recited in claim 20, wherein said shared controller comprises a Fibre Channel controller shared by the plurality of blade servers via said plurality of replicated programming interfaces.