This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

** Tags added: verification-needed-yakkety

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1663687

Title:
  [Hyper-V] Bug fixes for storvsc (tagged queuing, error conditions)

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Released

Bug description:
  Patchset:

  1/6 Enable tracking of queue depth.

  2/6 Remove the artificially imposed restriction on max segment size.

  3/6 Enable multi-q support. We will allocate the outgoing channel using
  the following policy:

          1. We will make every effort to pick a channel that is in the
             same NUMA node that is initiating the I/O
          2. The mapping between the guest CPU and the outgoing channel
             is persistent.

  4/6 Properly set SRB flags when hosting device supports tagged queuing.
  This patch improves the performance on Fiber Channel disks.

  5/6 When sense message is present on error, we should pass along to the upper
  layer to decide how to deal with the error.
  This patch fixes connectivity issues with Fiber Channel devices.

  6/6 On I/O errors, the Windows driver doesn't set data_transfer_length
  on error conditions other than SRB_STATUS_DATA_OVERRUN.
  In these cases we need to set data_transfer_length to 0,
  indicating there is no data transferred. On SRB_STATUS_DATA_OVERRUN,
  data_transfer_length is set by the Windows driver to the actual data 
transferred.

  The new feature (multi-q) in this patchset require boot line
  parameters to enable so they are safe to integrate.

  K. Y. Srinivasan (3):
    storvsc: Enable tracking of queue depth
    storvsc: Remove the restriction on max segment size
    storvsc: Enable multi-queue support

  Long Li (3):
    storvsc: use tagged SRB requests if supported by the device
    storvsc: properly handle SRB_ERROR when sense message is present
    storvsc: properly set residual data length on errors

  https://git.kernel.org/cgit/linux/kernel/git/next/linux-
  next.git/commit/?id=40630f462824ee24bc00d692865c86c3828094e0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1663687/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to