Skip to content

Introduce a driver to support host accelerated access to Microsoft Azure Blob for Azure VM

[email protected] linux-block linux-doc linux-hyperv lkml 5 versions – In review

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v5 Latest3 patches 31 repliesIn review
  2. v43 patches 19 repliesSuperseded
  3. v33 patches 16 repliesSuperseded
Earlier versions · 2
VersionPostedPatchesRepliesStatus
v23 patches24 repliesSuperseded
v12 patches8 repliesSuperseded

Changes in v5 from the cover letter

Added problem statement and test numbers to patch 0
Changed uapi header file to explicitly include all header files needed for user-mode Make the driver handle vmbus rescind without waiting on user-mode for device removal

Patches in v5 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/3Drivers: hv: vmbus: add support to ignore certain PCIE devicesdrivers/hv/channel_mgmt.c+42 -60 replies
2/3Drivers: hv: add Azure Blob driverDocumentation/userspace-api/ioctl/ioctl-number.rst drivers/hv/Kconfig drivers/hv/Makefile +4 more+639 -07 replies
3/3Drivers: hv: Add to maintainer for Hyper-V/Azure driversMAINTAINERS+2 -00 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v5 yet.

Read the v5 thread

Cover letter [Patch v5 0/3] Introduce a driver to support host accelerated access to Microsoft Azure Blob for Azure VM

From: Long Li <[email protected]>

Azure Blob storage [1] is Microsoft's object storage solution for the cloud. Users or client applications can access objects in Blob storage via HTTP, from anywhere in the world. Objects in Blob storage are accessible via the Azure Storage REST API, Azure PowerShell, Azure CLI, or an Azure Storage client library. The Blob storage interface is not designed to be a POSIX compliant interface.

Problem: When a client accesses Blob storage via HTTP, it must go through the Blob storage boundary of Azure and get to the storage server through multiple servers. This is also true for an Azure VM.

Solution: For an Azure VM, the Blob storage access can be accelerated by having Azure host execute the Blob storage requests to the backend storage server directly.

This driver implements a VSC (Virtual Service Client) for accelerating Blob storage access for an Azure VM by communicating with a VSP (Virtual Service Provider) on the Azure host. Instead of using HTTP to access the Blob storage, an Azure VM passes the Blob storage request to the VSP on the Azure host. The Azure host uses its native network to perform Blob storage requests to the backend server directly.

This driver doesn’t implement Blob storage APIs. It acts as a fast channel to pass user-mode Blob storage requests to the Azure host. The user-mode program using this driver implements Blob storage APIs and packages the Blob storage request as structured data to VSC. The request data is modeled as three user provided buffers (request, response and data buffers), that are patterned on the HTTP model used by existing Azure Blob clients. The VSC passes those buffers to VSP for Blob storage requests.

The driver optimizes Blob storage access for an Azure VM in two ways:

1. The Blob storage requests are performed by the Azure host to the Azure Blob backend storage server directly.

2. It allows the Azure host to use transport technologies (e.g. RDMA) available to the Azure host but not available to the VM, to reach to Azure Blob backend servers.

Test results using this driver for an Azure VM:
100 Blob clients running on an Azure VM, each reading 100GB Block Blobs. (10 TB total read data)
With REST API over HTTP: 94.4 mins
Using this driver: 72.5 mins
Performance (measured in throughput) gain: 30%.

[1] https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-introduction

Cc Jonathan Corbet <[email protected]>
Cc "K. Y. Srinivasan" <[email protected]>
Cc Haiyang Zhang <[email protected]>
Cc Stephen Hemminger <[email protected]>
Cc Wei Liu <[email protected]>
Cc Dexuan Cui <[email protected]>
Cc Greg Kroah-Hartman <[email protected]>
Cc Bjorn Andersson <[email protected]>
Cc Hans de Goede <[email protected]>
Cc Dan Williams <[email protected]>
Cc Maximilian Luz <[email protected]>
Cc Mike Rapoport <[email protected]>
Cc Ben Widawsky <[email protected]>
Cc Jiri Slaby <[email protected]>
Cc Andra Paraschiv <[email protected]>
Cc Siddharth Gupta <[email protected]>
Cc Hannes Reinecke <[email protected]>

Changes:

v2:
Refactored the code in vmbus to scan devices
Reworked Azure Blob driver and moved user-mode interfaces to uapi

v3:
Changed licensing language
Patch format passed "checkpatch --strict"
debugfs and logging, module parameter cleanup
General code clean up
Fix device removal race conditions

v4:
Addressed licencing issues
Changed to dynamic device model

v5:
Added problem statement and test numbers to patch 0
Changed uapi header file to explicitly include all header files needed for user-mode Make the driver handle vmbus rescind without waiting on user-mode for device removal

Long Li (3):
Drivers: hv: vmbus: add support to ignore certain PCIE devices
Drivers: hv: add Azure Blob driver
Drivers: hv: Add to maintainer for Hyper-V/Azure drivers

 Documentation/userspace-api/ioctl/ioctl-number.rst |   2 +
 MAINTAINERS                                        |   2 +
 drivers/hv/Kconfig                                 |  11 +
 drivers/hv/Makefile                                |   1 +
 drivers/hv/channel_mgmt.c                          |  55 +-
 drivers/hv/hv_azure_blob.c                         | 574 +++++++++++++++++++++
 include/linux/hyperv.h                             |   9 +
 include/uapi/misc/hv_azure_blob.h                  |  35 ++
 8 files changed, 683 insertions(+), 6 deletions(-)
 create mode 100644 drivers/hv/hv_azure_blob.c
 create mode 100644 include/uapi/misc/hv_azure_blob.h
Signature · 1 line
1.8.3.1