Patent Grant
10621133
The field of the invention is data processing, or, more specifically, methods, apparatus, and products for managing flexible adapter configurations in a computer system.
The development of the EDVAC computer system of 1948 is often cited as the beginning of the computer era. Since that time, computer systems have evolved into extremely complicated devices. Today's computers are much more sophisticated than early systems such as the EDVAC. Computer systems typically include a combination of hardware and software components, application programs, operating systems, processors, buses, memory, input/output devices, and so on. As advances in semiconductor processing and computer architecture push the performance of the computer higher and higher, more sophisticated computer software has evolved to take advantage of the higher performance of the hardware, resulting in computer systems today that are much more powerful than just a few years ago.
Methods, systems, and apparatus for managing flexible adapter configurations in a computer system are disclosed in this specification. Managing flexible adapter configurations in a computer system includes assigning an initial amount of resources to a set of empty expansion bus slots of the computer system; detecting an adapter has been attached to one of the set of empty expansion bus slots; receiving, by a hypervisor, a request for additional resources for use by the detected adapter, wherein the additional resources are in addition to the initial amount of resources assigned to the expansion bus slot occupied by the detected adapter; determining, by the hypervisor, an availability of the additional resources for the detected adapter; in response to determining that the additional resources are available for the detected adapter, assigning, by the hypervisor at runtime, the requested additional resources to the detected adapter.
The foregoing and other objects, features and advantages of the invention will be apparent from the following more particular descriptions of exemplary embodiments of the invention as illustrated in the accompanying drawings wherein like reference numbers generally represent like parts of exemplary embodiments of the invention.
Exemplary methods, apparatus, and products for managing flexible adapter configurations in a computer system in accordance with the present invention are described with reference to the accompanying drawings, beginning with
The example data center (120) of
Stored in RAM (168) is a hypervisor (136) and a management console (138). The management console (138) may provide a user interface through which a user may direct the hypervisor (136) on instantiating and maintaining multiple logical partitions (116, 118), where each logical partition may provide virtualization services to one or more clients.
Also stored in RAM (168) are two instances of an operating system (154), one for each logical partition (116, 118). Operating systems useful in computers configured for firmware management of SR-IOV adapters according to various embodiments include UNIX™, Linux™, Microsoft Windows™, AIX™, IBM's i™ operating system, and others as will occur to those of skill in the art. The operating systems (154), hypervisor (136), and management console (138) are shown in RAM (168), but many components of such software may typically be stored in non-volatile memory such as, for example, on a data storage (170) device or in firmware (132).
The computing system (102) may also include a storage device adapter (172) coupled through expansion bus (160) and bus adapter (158) to processor (156) and other components of the computing system (102). Storage device adapter (172) connects non-volatile data storage to the computing system (102) in the form of data storage (170). Storage device adapters useful in computers configured for managing flexible adapter configurations in a computer system according to various embodiments include Integrated Drive Electronics (“IDE”) adapters, Small Computing system Interface (“SCSI”) adapters, and others as will occur to those of skill in the art. Non-volatile computer memory also may be implemented for as an optical disk drive, electrically erasable programmable read-only memory (so-called “EEPROM” or “Flash” memory), RAM drives, and so on, as will occur to those of skill in the art.
The example computing system (102) may also include one or more input/output (“I/O”) adapters (178). I/O adapters implement user-oriented input/output through, for example, software drivers and computer hardware for controlling output to display devices such as computer display screens, as well as user input from user input devices (181) such as keyboards and mice. The example computing system (102) may also include a video adapter (114), which may be an example of an I/O adapter specially designed for graphic output to a display device (180) such as a display screen or computer monitor. Video adapter (114) may be connected to processor (156) through a high speed video bus (164), bus adapter (158), and the front side bus (162), which may also be a high speed bus.
The expansion bus (160) shown in
SR-IOV is an extension to the PCI Express (PCIe) specification. SR-IOV allows a device, such as a network adapter, to separate access to its resources among various PCIe hardware functions. These functions consist of the following types: A PCIe Physical Function (PF) and a PCIe Virtual Function (VF). The PF advertises the device's SR-IOV capabilities. Each VF is associated with a device's PF. A VF shares one or more physical resources of the device, such as a memory and a network port, with the PF and other VFs on the device. From the perspective of a logical partition (116, 118) instantiated by a hypervisor (136), a VF appears as a fully functional physical PCIe adapter. In this way, a single physical adapter may be ‘shared’ amongst many logical partitions or multiple virtual functions may be instantiated for use by a single logical partition. Although referred to as a ‘virtual’ function, readers of skill in the art will recognize that a VF is in fact a physical channel that is not a resource virtualized entirely by the hypervisor.
As a result of multiple LPAR sharing access to a single SR-IOV adapter, each SR-IOV adapter may require a greater number of resources relative to other types of adapters. Instead of requiring that such an adapter be plugged into specific slots of the communications fabric with an appropriate amount of resources already assigned, each empty slot in the communications fabric may be assigned or have reserved an initial or minimal amount of resources. Once an adapter is plugged in, a request for additional resources for that adapter is generated and the necessary additional resources are then assigned to that adapter.
The resources assigned to and reserved for the adapters attached to the communications fabric include partitional endpoint (PE) numbers, bus/device/function (BDF) ranges, memory mapping input/output (MMIO) addresses, direct memory access (DMA) addresses, and message signal interrupt (MSI) addresses.
For further explanation,
The same initial amount of resources may be assigned or reserved for each slot in the communications fabric. The initial amount of resources may be a minimal amount of resources, such that all or most adapters attached to the communications fabric will require at least the minimal amount of resources to function. For example, a PCIe fabric may include three empty expansion slots. Each of the three empty expansion slots may be assigned one PE number, one MIMIO window, and 256 MSI addresses.
The resource allocation may be tracked by the hypervisor using slot resource array data structures. The slot resource arrays store information that maps resources and resource ranges to expansion bus slots. The hypervisor may maintain one slot resource array for each type of resource assigned to the adapters.
The resources may be assigned to the empty expansion bus slots non-contiguously. Specifically, resources may be assigned such that a set of resources may be left unassigned between the sets of resources assigned to two empty expansion bus slots. The unassigned resources may be later assigned to one of the two expansion bus slots based on the requirements of the adapter. This increases the likelihood of an adapter being assigned a contiguous range of resources. For example, MSI addresses 1-255 may be initially assigned to a first expansion bus slot, and MSI addresses 864-1119 may be initially assigned to a second expansion bus slot. MSI addresses 256-863 would therefore be available to assign at a later time to adapters in either expansion bus slot providing a contiguous range of MSI address to the adapter.
The method of
An adapter requiring a relatively large number of resources need not be attached to a specific empty expansion bus slot. An initial amount of resources is assigned to each slot of the expansion bus, and additional resources are assigned, at runtime, to the adapter as required.
The method of
The method of
For example, determining (208), by the hypervisor (136), an availability of the additional resources for the detected adapter may be carried out by checking the number of VFs requested against the available contiguous PE number range size, checking the number of MSIs against the amount already assigned, checking the number of MSIs against the available unassigned region of MSIs, checking the number of MMIO windows against a limit for the expansion bus slot, and/or checking the number of MMIO windows against the PCI host bridge limit.
The method of
Determining that the additional resources are available may include, for example, determining that the number of VFs requested are available as a contiguous PE number range, determining that the number of MSIs is less than the amount already assigned, determining that the number of MSIs are available in the unassigned region of MSIs, determining that the number of MMIO windows is within a limit for the expansion bus slot, and/or determining that the number of MMIO windows is less than or equal to the PCI host bridge limit.
“At runtime” refers to a state of execution of the programs executing on the computer system, including the hypervisor. Assigning, by the hypervisor at runtime, resources to an adapter may indicate that the resources are assigned to the adapter without restarting the hypervisor or placing the hypervisor in a suspended state. Assigning, by the hypervisor at runtime, resources to an adapter may also indicate that the resources are assigned to the adapter while the hypervisor is in a state of execution.
For further explanation,
The method of
Determining that the additional resources are not available may include, for example, determining that the number of VFs requested are not available as a contiguous PE number range, determining that the number of MSIs is greater than the amount already assigned and determining that the number of additional MSIs are not available in the unassigned region of MSIs, determining that the number of MMIO windows is not within a limit for the expansion bus slot, and/or determining that the number of MMIO windows is greater than the PCI host bridge limit.
For further explanation,
The method of
For further explanation,
The method of
Receiving (206), by a hypervisor (136), a request for additional resources for use by the detected adapter, wherein the additional resources are in addition to the initial amount of resources assigned to the expansion bus slot occupied by the detected adapter also includes determining (504) an amount of required resources for the detected adapter. Determining (504) an amount of required resources for the detected adapter may be carried out by inspecting a configuration file stored on the adapter and locating information that includes a specification of the necessary resources required to operate the adapter.
Determining (504) an amount of required resources for the detected adapter may also be carried out by calculating the amount of required resources based on the initial amount of resources already assigned to the adapter. For example, the initial amount of resources may be subtracted from the amount of required resources for the adapter to determine the amount of additional resources to assign to the adapter.
Receiving (206), by a hypervisor (136), a request for additional resources for use by the detected adapter, wherein the additional resources are in addition to the initial amount of resources assigned to the expansion bus slot occupied by the detected adapter also includes determining (506) that the required resources are greater than the initial amount of resources assigned to the detected adapter. Determining (506) that the required resources are greater than the initial amount of resources assigned to the detected adapter may be carried out by comparing the amount of required resources to the initial amount of resources previously assigned to the expansion bus slot.
For example, an empty expansion bus slot may be initially assigned 256 MSI addresses. An adapter attached to the empty slot may include a configuration file indicating that the adapter requires, among other things, at least 864 MSI addresses. The hypervisor may then determine that 608 additional MSI address should be assigned to the adapter.
For further explanation,
The method of
For example, virtual function partitionable endpoint number regions may be assigned in contiguous blocks for SR-IOV adapters. The total number of virtual function partitionable endpoint numbers on the PCI host bridge may be 256, and the highest 16 numbers may be reserved for physical functions. If there are three adapter slots on a communications fabric, the remaining virtual function partitionable endpoint numbers may be divided into three contiguous segments (0-79, 80-159, and 160-239). Each empty bus slot may be initially assigned 3 virtual function partitionable endpoints from each corresponding segment. Once a SR-IOV adapter is plugged into the communications fabric, the request for additional resources may be serviced by assigning resources from the corresponding segment. Specifically, the hypervisor may assign the next adjacent numbers to the numbers already assigned to the expansion bus slot.
In view of the explanations set forth above, readers will recognize that the benefits of managing flexible adapter configurations in a computer system according to embodiments of the present invention include:
Exemplary embodiments of the present invention are described largely in the context of a fully functional computer system for managing flexible adapter configurations in a computer system. Readers of skill in the art will recognize, however, that the present invention also may be embodied in a computer program product disposed upon computer readable storage media for use with any suitable data processing system. Such computer readable storage media may be any storage medium for machine-readable information, including magnetic media, optical media, or other suitable media. Examples of such media include magnetic disks in hard drives or diskettes, compact disks for optical drives, magnetic tape, and others as will occur to those of skill in the art. Persons skilled in the art will immediately recognize that any computer system having suitable programming means will be capable of executing the steps of the method of the invention as embodied in a computer program product. Persons skilled in the art will recognize also that, although some of the exemplary embodiments described in this specification are oriented to software installed and executing on computer hardware, nevertheless, alternative embodiments implemented as firmware or as hardware are well within the scope of the present invention.
The present invention may be a system, a method, and/or a computer program product. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.
The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++ or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.
Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.
These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.
It will be understood from the foregoing description that modifications and changes may be made in various embodiments of the present invention without departing from its true spirit. The descriptions in this specification are for purposes of illustration only and are not to be construed in a limiting sense. The scope of the present invention is limited only by the language of the following claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 8001313 | Eggers | Aug 2011 | B2 |
| 8161260 | Srinivasan | Apr 2012 | B2 |
| 8473947 | Goggin | Jun 2013 | B2 |
| 8645755 | Brownlow et al. | Feb 2014 | B2 |
| 9218195 | Anderson et al. | Dec 2015 | B2 |
| 9600339 | Challa | Mar 2017 | B2 |
| 9716361 | Huang et al. | Jul 2017 | B2 |
| 10203991 | Brady | Feb 2019 | B2 |
| 10228962 | Dornemann | Mar 2019 | B2 |
| 20090037941 | Armstrong | Feb 2009 | A1 |
| 20110035519 | Dean et al. | Feb 2011 | A1 |
| 20160065484 | Suzuki et al. | Mar 2016 | A1 |
| 20160124774 | Antony | May 2016 | A1 |
| 20160147657 | Jiang | May 2016 | A1 |
| Entry |
|---|
| BIOS Central, “BIOS Basics”, bioscentral.com (online), [accessed Dec. 12, 2016], 2 Pages, URL: www.bioscentral.com/misc/biosbasics.htm. |
| Intel, “Intel® Platform Innovation Framework for EFI PCI Host Bridge Resource Allocation Protocol Specification”, Version 0.9, Aug. 9, 2004, intel.co.uk (online); URL: www.intel.co.uk/content/dam/doc/reference-guide/efi-pci-host-bridge-allocation-protocol-specification.pdf. |
| U.S. Appl. No. 16/580,282, to Jesse P. Arroyo et al., entitled, Managing Flexible Adapter Configurations in a Computer System, assigned to International Business Machines Corporation, 30 pages, filed Sep. 24, 2019. |
| Appendix P; List of IBM Patent or Applications Treated as Related, Dec. 19, 2019, 2 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20180225250 A1 | Aug 2018 | US |
