← Back to team overview

group.of.nepali.translators team mailing list archive

[Bug 1745260] Re: [Hyper-V] scsi: storvsc: Spread interrupts when picking a channel for I/O requests

 

This bug was fixed in the package linux-azure - 4.13.0-1009.12

---------------
linux-azure (4.13.0-1009.12) xenial; urgency=low

  * linux-azure: 4.13.0-1009.12 -proposed tracker (LP: #1746726)

  * libata: apply MAX_SEC_1024 to all LITEON EP1 series devices (LP: #1743053)
    - libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

linux-azure (4.13.0-1008.11) xenial; urgency=low

  * linux-azure: 4.13.0-1008.11 -proposed tracker (LP: #1745669)

  * [Hyper-V] x86/hyperv: Stop suppressing X86_FEATURE_PCID (LP: #1745247)
    - x86/hyperv: Stop suppressing X86_FEATURE_PCID

  * [Hyper-V] scsi: storvsc: Spread interrupts when picking a channel for I/O
    requests (LP: #1745260)
    - SAUCE: scsi: storvsc: Spread interrupts when picking a channel for I/O
      requests

  * [Hyper-V] scsi: storvsc: Increase cmd_per_lun for higher speed devices
    (LP: #1745261)
    - SAUCE: scsi: storvsc: Increase cmd_per_lun for higher speed devices
    - [Config] CONFIG_SCSI_MQ_DEFAULT=y

 -- Marcelo Henrique Cerri <marcelo.cerri@xxxxxxxxxxxxx>  Thu, 01 Feb
2018 11:13:09 -0200

** Changed in: linux-azure (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1745260

Title:
  [Hyper-V] scsi: storvsc: Spread interrupts when picking a channel for
  I/O requests

Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Committed

Bug description:
  Update the algorithm in storvsc_do_io to look for a channel
  starting with the current CPU + 1 and wrap around (within the
  current NUMA node). This spreads VMbus interrupts more evenly
  across CPUs. Previous code always started with first CPU in
  the current NUMA node, skewing the interrupt load to that CPU.

  This should be applied to the linux-azure kernel

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