Activity log for bug #1801305

Date Who What changed Old value New value Message
2018-11-02 07:16:10 Daniel Axtens bug added bug
2018-11-02 07:16:37 Daniel Axtens description In current Ubuntu kernels, PV blkfront drivers have blk-mq enabled by default. [Impact] blk-mq is not as fast as the old request-based scheduler for some workloads on HDD disks. [Fix] Amazon Linux has a commit which reintroduces the request-based mode. It disables blk-mq by default but allows it to be switched back on with a kernel parameter. [Regression Potential] Could potentially break xen based disks on AWS. For B/C, the patches also add some code to the xen core around suspend and resume, this code is much smaller and also mirrors code already in Xenial. [Tests] Tested by AWS for Xenial, and their kernel engineers vetted the patches. I tested the Bionic and Cosmic patchsets with fio, the system appears stable and the IOPS promised for EBS Provisioned IOPS disks were met in my testing. In current Ubuntu kernels, PV blkfront drivers have blk-mq enabled by default and cannot use the old I/O scheduler. [Impact] blk-mq is not as fast as the old request-based scheduler for some workloads on HDD disks. [Fix] Amazon Linux has a commit which reintroduces the request-based mode. It disables blk-mq by default but allows it to be switched back on with a kernel parameter. [Regression Potential] Could potentially break xen based disks on AWS. For B/C, the patches also add some code to the xen core around suspend and resume, this code is much smaller and also mirrors code already in Xenial. [Tests] Tested by AWS for Xenial, and their kernel engineers vetted the patches. I tested the Bionic and Cosmic patchsets with fio, the system appears stable and the IOPS promised for EBS Provisioned IOPS disks were met in my testing.
2018-11-02 07:17:37 Daniel Axtens description In current Ubuntu kernels, PV blkfront drivers have blk-mq enabled by default and cannot use the old I/O scheduler. [Impact] blk-mq is not as fast as the old request-based scheduler for some workloads on HDD disks. [Fix] Amazon Linux has a commit which reintroduces the request-based mode. It disables blk-mq by default but allows it to be switched back on with a kernel parameter. [Regression Potential] Could potentially break xen based disks on AWS. For B/C, the patches also add some code to the xen core around suspend and resume, this code is much smaller and also mirrors code already in Xenial. [Tests] Tested by AWS for Xenial, and their kernel engineers vetted the patches. I tested the Bionic and Cosmic patchsets with fio, the system appears stable and the IOPS promised for EBS Provisioned IOPS disks were met in my testing. In current Ubuntu kernels, PV blkfront drivers have blk-mq enabled by default and cannot use the old I/O scheduler. [Impact] blk-mq is not as fast as the old request-based scheduler for some workloads on HDD disks. [Fix] Amazon Linux has a commit which reintroduces the request-based mode. It disables blk-mq by default but allows it to be switched back on with a kernel parameter. [Regression Potential] Could potentially break xen based disks on AWS. For B/C, the patches also add some code to the xen core around suspend and resume, this code is much smaller and also mirrors code already in Xenial. [Tests] Tested by AWS for Xenial, and their kernel engineers vetted the patches. I tested the Bionic and Cosmic patchsets with fio, the system appears stable and the IOPS promised for EBS Provisioned IOPS disks were met in my testing. I did an apt update/upgrade and everything worked (no hash-sum mismatches).
2018-11-02 07:26:01 Daniel Axtens description In current Ubuntu kernels, PV blkfront drivers have blk-mq enabled by default and cannot use the old I/O scheduler. [Impact] blk-mq is not as fast as the old request-based scheduler for some workloads on HDD disks. [Fix] Amazon Linux has a commit which reintroduces the request-based mode. It disables blk-mq by default but allows it to be switched back on with a kernel parameter. [Regression Potential] Could potentially break xen based disks on AWS. For B/C, the patches also add some code to the xen core around suspend and resume, this code is much smaller and also mirrors code already in Xenial. [Tests] Tested by AWS for Xenial, and their kernel engineers vetted the patches. I tested the Bionic and Cosmic patchsets with fio, the system appears stable and the IOPS promised for EBS Provisioned IOPS disks were met in my testing. I did an apt update/upgrade and everything worked (no hash-sum mismatches). In current Ubuntu kernels, PV blkfront drivers have blk-mq enabled by default and cannot use the old I/O scheduler. [Impact] blk-mq is not as fast as the old request-based scheduler for some workloads on HDD disks. [Fix] Amazon Linux has a commit which reintroduces the request-based mode. It disables blk-mq by default but allows it to be switched back on with a kernel parameter. For B/C this patchset is bigger as it includes the suspend/resume patches already in X, and a new fixup. These are desirable as the request mode patch assumes their presence. [Regression Potential] Could potentially break xen based disks on AWS. For B/C, the patches also add some code to the xen core around suspend and resume, this code is much smaller and also mirrors code already in Xenial. [Tests] Tested by AWS for Xenial, and their kernel engineers vetted the patches. I tested the Bionic and Cosmic patchsets with fio, the system appears stable and the IOPS promised for EBS Provisioned IOPS disks were met in my testing. I did an apt update/upgrade and everything worked (no hash-sum mismatches).
2018-11-02 07:27:28 Daniel Axtens description In current Ubuntu kernels, PV blkfront drivers have blk-mq enabled by default and cannot use the old I/O scheduler. [Impact] blk-mq is not as fast as the old request-based scheduler for some workloads on HDD disks. [Fix] Amazon Linux has a commit which reintroduces the request-based mode. It disables blk-mq by default but allows it to be switched back on with a kernel parameter. For B/C this patchset is bigger as it includes the suspend/resume patches already in X, and a new fixup. These are desirable as the request mode patch assumes their presence. [Regression Potential] Could potentially break xen based disks on AWS. For B/C, the patches also add some code to the xen core around suspend and resume, this code is much smaller and also mirrors code already in Xenial. [Tests] Tested by AWS for Xenial, and their kernel engineers vetted the patches. I tested the Bionic and Cosmic patchsets with fio, the system appears stable and the IOPS promised for EBS Provisioned IOPS disks were met in my testing. I did an apt update/upgrade and everything worked (no hash-sum mismatches). In current Ubuntu kernels, PV blkfront drivers have blk-mq enabled by default and cannot use the old I/O scheduler. [Impact] blk-mq is not as fast as the old request-based scheduler for some workloads on HDD disks. [Fix] Amazon Linux has a commit which reintroduces the request-based mode. It disables blk-mq by default but allows it to be switched back on with a kernel parameter. For X this needs a small patch from upstream for error handling. For B/C this patchset is bigger as it includes the suspend/resume patches already in X, and a new fixup. These are desirable as the request mode patch assumes their presence. [Regression Potential] Could potentially break xen based disks on AWS. For B/C, the patches also add some code to the xen core around suspend and resume, this code is much smaller and also mirrors code already in Xenial. [Tests] Tested by AWS for Xenial, and their kernel engineers vetted the patches. I tested the Bionic and Cosmic patchsets with fio, the system appears stable and the IOPS promised for EBS Provisioned IOPS disks were met in my testing. I did an apt update/upgrade and everything worked (no hash-sum mismatches).
2018-11-08 06:07:57 Khaled El Mously linux (Ubuntu): status Confirmed Fix Committed
2018-11-09 09:54:29 Mauricio Faria de Oliveira bug added subscriber Mauricio Faria de Oliveira
2018-11-21 16:36:21 Kamal Mostafa nominated for series Ubuntu Trusty
2018-11-21 16:36:21 Kamal Mostafa bug task added linux (Ubuntu Trusty)
2018-11-21 16:36:21 Kamal Mostafa nominated for series Ubuntu Disco
2018-11-21 16:36:21 Kamal Mostafa bug task added linux (Ubuntu Disco)
2018-11-21 16:36:21 Kamal Mostafa nominated for series Ubuntu Xenial
2018-11-21 16:36:21 Kamal Mostafa bug task added linux (Ubuntu Xenial)
2018-11-21 16:36:21 Kamal Mostafa nominated for series Ubuntu Bionic
2018-11-21 16:36:21 Kamal Mostafa bug task added linux (Ubuntu Bionic)
2018-11-21 16:36:21 Kamal Mostafa nominated for series Ubuntu Cosmic
2018-11-21 16:36:21 Kamal Mostafa bug task added linux (Ubuntu Cosmic)
2018-11-21 16:36:36 Kamal Mostafa linux (Ubuntu Disco): status Fix Committed Triaged
2018-11-21 16:36:40 Kamal Mostafa linux (Ubuntu Cosmic): status New Fix Committed
2018-11-21 16:36:43 Kamal Mostafa linux (Ubuntu Bionic): status New Fix Committed
2018-11-21 16:36:46 Kamal Mostafa linux (Ubuntu Xenial): status New Fix Committed
2018-11-21 16:36:48 Kamal Mostafa linux (Ubuntu Trusty): status New In Progress
2018-11-21 17:57:13 Kamal Mostafa linux (Ubuntu Trusty): status In Progress Fix Committed
2018-12-21 17:14:22 Kamal Mostafa bug task added linux-aws (Ubuntu)
2018-12-21 17:14:38 Kamal Mostafa bug task deleted linux (Ubuntu)
2018-12-21 17:14:52 Kamal Mostafa linux-aws (Ubuntu Trusty): status New Fix Released
2018-12-21 17:15:01 Kamal Mostafa linux-aws (Ubuntu Xenial): status New Fix Released
2018-12-21 17:15:09 Kamal Mostafa linux-aws (Ubuntu Bionic): status New Fix Released
2018-12-21 17:15:17 Kamal Mostafa linux-aws (Ubuntu Cosmic): status New Fix Released
2018-12-21 17:15:25 Kamal Mostafa linux-aws (Ubuntu Disco): status New Fix Released
2020-07-02 19:55:35 Steve Langasek linux (Ubuntu Disco): status Triaged Won't Fix