linux-hyperv.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: longli@linuxonhyperv.com
To: linux-kernel@vger.kernel.org, linux-hyperv@vger.kernel.org
Cc: Long Li <longli@microsoft.com>
Subject: [Patch v3 0/3] Introduce a driver to support host accelerated access to Microsoft Azure Blob
Date: Tue, 13 Jul 2021 19:45:19 -0700	[thread overview]
Message-ID: <1626230722-1971-1-git-send-email-longli@linuxonhyperv.com> (raw)

From: Long Li <longli@microsoft.com>

Microsoft Azure Blob storage service exposes a REST API to applications
for data access. While it's flexible and works on most platforms, it's
not as efficient as native network stack.

This patchset implements a VSC that communicates with a VSP on the host
to execute blob storage access via native network stack on the host.

Reference:
https://azure.microsoft.com/en-us/services/storage/blobs/#overview



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 Azure Blob driver

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


 Documentation/userspace-api/ioctl/ioctl-number.rst |   2 +
 MAINTAINERS                                        |   1 +
 drivers/hv/Kconfig                                 |  10 +
 drivers/hv/Makefile                                |   1 +
 drivers/hv/azure_blob.c                            | 625 +++++++++++++++++++++
 drivers/hv/channel_mgmt.c                          |  55 +-
 include/linux/hyperv.h                             |   9 +
 include/uapi/misc/azure_blob.h                     |  34 ++
 8 files changed, 731 insertions(+), 6 deletions(-)
 create mode 100644 drivers/hv/azure_blob.c
 create mode 100644 include/uapi/misc/azure_blob.h

-- 
1.8.3.1


             reply	other threads:[~2021-07-14  2:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-14  2:45 longli [this message]
2021-07-14  2:45 ` [Patch v3 1/3] Drivers: hv: vmbus: add support to ignore certain PCIE devices longli
2021-07-16 14:33   ` Michael Kelley
2021-07-14  2:45 ` [Patch v3 2/3] Drivers: hv: add Azure Blob driver longli
2021-07-14 17:23   ` Greg Kroah-Hartman
2021-07-14 21:14     ` Long Li
2021-07-15  8:19       ` Greg Kroah-Hartman
2021-07-14 17:25   ` Greg Kroah-Hartman
2021-07-14 17:26   ` Greg Kroah-Hartman
2021-07-14 22:13     ` Long Li
2021-07-14 17:27   ` Greg Kroah-Hartman
2021-07-14 21:23     ` Long Li
2021-07-16 15:56   ` Michael Kelley
2021-07-16 17:28     ` Greg Kroah-Hartman
2021-07-16 19:29       ` Long Li
2021-07-16 19:26     ` Long Li
2021-07-16 21:06       ` Michael Kelley
2021-07-16 21:19         ` Long Li
2021-07-14  2:45 ` [Patch v3 3/3] Drivers: hv: Add to maintainer for " longli
2021-07-15  8:21   ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1626230722-1971-1-git-send-email-longli@linuxonhyperv.com \
    --to=longli@linuxonhyperv.com \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longli@microsoft.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).