• Skip to main content
  • Skip to primary sidebar
  • Home
  • About
    • Stephen Foskett
      • My Publications
        • Urban Forms in Suburbia: The Rise of the Edge City
      • Storage Magazine Columns
      • Whitepapers
      • Multimedia
      • Speaking Engagements
    • Services
    • Disclosures
  • Categories
    • Apple
    • Ask a Pack Rat
    • Computer History
    • Deals
    • Enterprise storage
    • Events
    • Personal
    • Photography
    • Terabyte home
    • Virtual Storage
  • Guides
    • The iPhone Exchange ActiveSync Guide
      • The iPhone Exchange ActiveSync Troubleshooting Guide
    • The iPad Exchange ActiveSync Guide
      • iPad Exchange ActiveSync Troubleshooting Guide
    • Toolbox
      • Power Over Ethernet Calculator
      • EMC Symmetrix WWN Calculator
      • EMC Symmetrix TimeFinder DOS Batch File
    • Linux Logical Volume Manager Walkthrough
  • Calendar

Stephen Foskett, Pack Rat

Understanding the accumulation of data

You are here: Home / Everything / Computer History / The I/O Blender Part 3: Behold the Power of the Demultiplexer

The I/O Blender Part 3: Behold the Power of the Demultiplexer

May 25, 2012 By Stephen 3 Comments

Virtualization has disrupted the I/O path, reducing the value of enterprise storage arrays. But all is not lost: An effort is afoot to make things right by increasing communication between hypervisor and array and demultiplexing data before it is stored.

VMware vVol is a necessary step to promote virtual disks to "full citizen" status

“What we have here is a failure to communicate”

The core problem with the I/O blender is that virtual machine disk images aren’t communicated or managed at the same level as “real” LUNs. This isn’t a surprise: They didn’t exist when today’s dominant storage protocols and arrays were designed!

Block storage protocols just aren’t capable of passing sufficient information between the hypervisor and the storage array. In the old days, this was not a problem because the storage array could assume that any I/O on a given port, and any data stored on a given LUN, was from a single server. But this is no longer the case when the hypervisor maintains its own LUN presentation.

VMware and the major enterprise storage players had great success augmenting this communication channel with VAAI. This API allows the hypervisor to instruct the storage array to lock, zero out, or make a copy of a set of data independent of the LUN. In practice, VAAI helps greatly to alleviate the pressure on storage arrays.

But the array still has insufficient information effectively to cache storage access. And VAAI integration does not make a virtual machine disk a “full citizen” when it comes to data management and manipulation in the array.

Emancipation of Virtual Machine Disks

VMware introduced a new idea at VMworld 2011 that would change everything about the I/O blender. Although not an official product, the so-called vVol concept would add a communication channel to allow storage arrays to de-multiplex I/O. In the vVol world, virtual machine disks can be treated just the same as conventional LUNs.

Note: vVol doesn’t have an official name yet. Hopefully it won’t be “VMware API Program for I/O Demux (VAPID)” though!

Contrary to the hysteria of last summer, it does not appear that VMware is introducing their own totally new storage protocol. Instead, vVol would be an out of band communication channel somewhat like VAAI, while conventional I/O operations would continue to use a protocol like SCSI or NFS.

Can Your Array Handle vVol?

But this does not mean that any old storage array can support vVol. On the contrary, this promises to be a very tricky implementation indeed. The storage array must not only support the vVol API or command set, it must also have the horsepower to demultiplex I/O and reassemble virtual machine disk images. Then, it must have sufficient capability to effectively manage these disk images internally.

One can imagine two alternatives for implementing vVol inside a storage array:

  1. The array can demultiplex on ingestion, storing virtual machine disks on the backend as plain old LUNs or files
  2. Or the array can maintain a mapping table for multiplexed data, adding a new layer of abstraction

Each array model will likely lend itself to one or the other solution, and storage vendors will have to choose the right mechanism for their device. But neither choice is easy, and both will require additional memory and CPU resources as well as a great deal of programming effort.

It may appear that NFS does not need vVol, but this is not the case. vVol is about more than just demultiplexing block storage access: It is about elevating the virtual machine disk image to “full citizen” status. If NFS didn’t need vVol, the entire industry wouldn’t need vVol; they could just adopt NFS!

Stephen’s Stance

It is not clear whether VMware will introduce vVol officially as part of the (presumably) forthcoming vSphere 6, and it will likely be a year or more before we see more than a few production-ready arrays. But addressing the issue of the I/O blender is too important to be ignored, and VMware should be commended for tackling the issue head-on.

You might also want to read these other posts...

  • Electric Car Over the Internet: My Experience Buying…
  • GPS Time Rollover Failures Keep Happening (But…
  • Introducing Rabbit: I Bought a Cloud!
  • Liberate Wi-Fi Smart Bulbs and Switches with Tasmota!
  • Running Rabbits: More About My Cloud NUCs

Filed Under: Computer History, Enterprise storage, Virtual Storage Tagged With: de-multiplex, I/O blender, LUN, NFS, VAAI, VMware, VMworld, vVol

Primary Sidebar

There can be no faith in government if our highest offices are excused from scrutiny – they should be setting the example of transparency.

Edward Snowden

Subscribe via Email

Subscribe via email and you will receive my latest blog posts in your inbox. No ads or spam, just the same great content you find on my site!
 New posts (daily)
 Where's Stephen? (weekly)

Download My Book


Download my free e-book:
Essential Enterprise Storage Concepts!

Recent Posts

Electric Car Over the Internet: My Experience Buying From Vroom

November 28, 2020

Powering Rabbits: The Mean Well LRS-350-12 Power Supply

October 18, 2020

Tortoise or Hare? Nvidia Jetson TK1

September 22, 2020

Running Rabbits: More About My Cloud NUCs

September 21, 2020

Introducing Rabbit: I Bought a Cloud!

September 10, 2020

Remove ROM To Use LSI SAS Cards in HPE Servers

August 23, 2020

Test Your Wi-Fi with iPerf for iOS

July 9, 2020

Liberate Wi-Fi Smart Bulbs and Switches with Tasmota!

May 29, 2020

What You See and What You Get When You Follow Me

May 28, 2019

GPS Time Rollover Failures Keep Happening (But They’re Almost Done)

April 6, 2019

Symbolic Links

    Featured Posts

    Review: 2013 Ford Flex

    September 23, 2012

    FCoE vs. iSCSI – Making the Choice

    May 20, 2011

    EMC Redefine Possible (TL;DR Edition)

    July 9, 2014

    Sony NEX-7 Hands-On Review Part 1: The New Super-Camera

    March 26, 2012

    Put that camera away and enjoy the view!

    April 11, 2012

    Download My Free E-Book, “Essential Enterprise Storage Concepts”!

    April 4, 2017

    Storage Changes in VMware vSphere 5

    July 16, 2011

    Microsoft’s Overlooked Innovation

    February 15, 2010

    The Fat Middle: Today’s Enterprise Storage Array

    August 31, 2014

    What’s the Difference Between a Jailbroken and an Unlocked Phone?

    May 5, 2012

    Copyright © 2021 · Log in