Towards the InfiniBand SR-IOV vSwitch Architecture

Tasoulas, Evangelos; Gran, Ernst Gunnar; Johnsen, Bjorn Dag; Begnum, Kyrre; Skeie, Tor

doi:10.1109/cluster.2015.58

Cited by 5 publications

(18 citation statements)

References 20 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…12 We used IB to demonstrate our concept prototypes and suggested different options that can help to overcome the scalability issues related to the layer-2 LID space address limitations of IB. 12 We used IB to demonstrate our concept prototypes and suggested different options that can help to overcome the scalability issues related to the layer-2 LID space address limitations of IB.…”

Section: Resultsmentioning

confidence: 99%

“…In this paper, we revisited and complemented our proposed vSwitch SR-IOV architecture for lossless interconnection networks. 12 We used IB to demonstrate our concept prototypes and suggested different options that can help to overcome the scalability issues related to the layer-2 LID space address limitations of IB. Routing strategies for vSwitch-based subnets were discussed and a Fat-Tree routing algorithm was presented, vSwitch-FatTree, which takes into account the shared connection of VMs residing at the same hypervisor.…”

Section: Resultsmentioning

confidence: 99%

“…In this work, we focus on the second group of challenges and address issues from the perspective of the network. In our previous work, 12 we proposed two implementations of the Virtual Switch (vSwitch) architecture, that allow IB subnets to support transparent virtualization and migration of all IB addresses, accompanied with a scalable and topology-agnostic dynamic network reconfiguration method to make live migrations of VMs feasible in large vSwitch-based IB subnets. * Each IB connected node has three different addresses: LID, GUID, and GID (further discussed in Section 2).…”

mentioning

confidence: 99%

“…12 Moreover, the reconfiguration algorithm presented in our previous work 12 (we call it ItRC in the rest of the paper) made live migrations feasible, but it was suboptimal. The space-domain scalability issues were left unaddressed.…”

mentioning

confidence: 99%

“…Summary of the proposed vSwitch architecture. Refer to our previous work12 for more details and formula explanations Takes more time to configure the network when Medium: Takes into account only the Initialization booting since paths have to be computed and distributed even physical infrastructureandthe number (Lower is better) if no VMs are running. of active VMs.…”

mentioning

confidence: 99%

See 4 more Smart Citations

Efficient routing and reconfiguration in virtualized HPC environments with vSwitch‐enabled lossless networks

Tasoulas

Zahid

Gran

et al. 2018

Concurrency and Computation

Self Cite

View full text Add to dashboard Cite

To meet the demands of communication-intensive workloads in the cloud, virtual machines (VMs) should utilize low overhead network communication paradigms. In general, such paradigms enable VMs to directly communicate with the hardware by means of a passthrough technology like Single-Root I/O Virtualization (SR-IOV). However, when passthrough-based virtualization is coupled with lossless interconnection networks, live migrations introduce scalability challenges due to the substantial network reconfiguration overhead. With these challenges in mind, we proposed a virtual switch (vSwitch) SR-IOV architecture for InfiniBand in our previous work titled "Towards the InfiniBand SR-IOV vSwitch Architecture". In this paper, we first suggest solutions to rectify the space-domain scalability issues that are present in vSwitch-enabled subnets as a result of the VMs using dedicated layer-two addresses. Then, we discuss routing strategies for virtualized environments using vSwitches and present a routing algorithm for Fat-Trees. We also present a reconfiguration method that minimizes imposed reconfiguration overhead on Fat-Trees.We perform an extensive evaluation of our prototype algorithms, and as vSwitch-enabled hardware does not yet exist, we deduce from empirical observations by emulating vSwitches with existing hardware, as well as large-scale simulations. Our results show significant reduction in the reconfiguration times as route recalculations can be eliminated, and for certain scenarios, the number of reconfiguration subnet management packets sent to switches is reduced from several hundred thousand down to a single one without degrading the routing quality.

show abstract

Section: Resultsmentioning

confidence: 99%

Section: Resultsmentioning

confidence: 99%

mentioning

confidence: 99%

mentioning

confidence: 99%

mentioning

confidence: 99%

See 3 more Smart Citations