• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Yellow Bricks

by Duncan Epping

  • Home
  • ESXTOP
  • Stickers/Shirts
  • Privacy Policy
  • About
  • Show Search
Hide Search

New white paper available: vSphere APIs for I/O Filtering (VAIO)

Duncan Epping · Oct 13, 2017 ·

Over the past couple of weeks Cormac Hogan and I have been updating various Core Storage white papers which had not been touched in a while for different reasons. We were starting to see more and more requests come in for update content and as both of used to be responsible for this at some point in the past we figured we would update the papers and then hand them over to technical marketing for “maintenance” updates in the future.

You can expect a whole series of papers in the upcoming weeks on storagehub.vmware.com and the first one was just published. It is on the topic of the vSphere APIs for I/O Filtering and provides an overview of what it is, where it sits in the I/O path and how you can benefit from it. I would suggest downloading the paper, or reading it online on storagehub:

  • vSphere APIs for I/O Filtering White Paper online
  • vSphere APIs for I/O Filtering White Paper download

Related

BC-DR, Server, Software Defined, Storage caching, replication, vaio, vSphere, vsphere apis for io filtering

Reader Interactions

Comments

  1. Jason says

    19 October, 2017 at 21:26

    Sony would like to have a word with you…

  2. Gautham says

    23 October, 2017 at 06:38

    Hi Duncan , Got a question from one of our customers setting up a bunch of SAP HANA servers on VMWare, all on flash.. so the rules are different. If the ESXi servers has 8 Connections to the Pure SAN, can I use one controller on my RHEL7 server, and expect the writes and reads to be split up between ESX and Pure? Dont want to have writes split up 2 times, causing an exponential increase in interrupts at the ESX level.. EX: one atomic OS write could be broken into 4 controllers. and each controllers sub write would be chopped up again when it goes from ESX to Pure.. So.. if I send one write to ESX, and it chops into 8 writes to pure, is it better than chopping into 4 writes at RHEL level, and then 8 chops for each, leaving 32 separate interrupts on ESX server?

    Appreciate if you revert to this question

Primary Sidebar

About the author

Duncan Epping is a Chief Technologist in the Office of CTO of the Cloud Platform BU at VMware. He is a VCDX (# 007), the author of the "vSAN Deep Dive", the “vSphere Clustering Technical Deep Dive” series, and the host of the "Unexplored Territory" podcast.

Upcoming Events

May 24th – VMUG Poland
June 1st – VMUG Belgium
Aug 21st – VMware Explore
Sep 20th – VMUG DK
Nov 6th – VMware Explore
Dec 7th – Swiss German VMUG

Recommended Reads

Sponsors

Want to support Yellow-Bricks? Buy an advert!

Advertisements

Copyright Yellow-Bricks.com © 2023 · Log in