| 2017-07-14 16:40:26 |
Alice Liu |
bug |
|
|
added bug |
| 2017-07-14 16:40:34 |
Alice Liu |
information type |
Proprietary |
Private |
|
| 2017-11-03 03:07:12 |
Alice Liu |
description |
Description
We already keep the sector in the radix tree as part of the exceptional entry. For page faults where we already have an exceptional entry, use this information directly from the radix tree instead of calling into the filesystem to get a block mapping. This should show a measurable performance improvement, which should be reported as motivation for the patches.
Target Kernel:4.14
Target Release: 18.04 |
Description
We already keep the sector in the radix tree as part of the exceptional entry. For page faults where we already have an exceptional entry, use this information directly from the radix tree instead of calling into the filesystem to get a block mapping. This should show a measurable performance improvement, which should be reported as motivation for the patches.
Target Kernel:4.16
Target Release: 18.04 |
|
| 2018-02-23 23:39:26 |
Leann Ogasawara |
intel: status |
New |
Incomplete |
|
| 2018-02-23 23:41:50 |
Leann Ogasawara |
tags |
|
kernel |
|
| 2018-03-20 06:56:18 |
quanxian |
description |
Description
We already keep the sector in the radix tree as part of the exceptional entry. For page faults where we already have an exceptional entry, use this information directly from the radix tree instead of calling into the filesystem to get a block mapping. This should show a measurable performance improvement, which should be reported as motivation for the patches.
Target Kernel:4.16
Target Release: 18.04 |
Description
We already keep the sector in the radix tree as part of the exceptional entry. For page faults where we already have an exceptional entry, use this information directly from the radix tree instead of calling into the filesystem to get a block mapping. This should show a measurable performance improvement, which should be reported as motivation for the patches.
Target Kernel:4.17
Target Release: 18.04 |
|
| 2018-05-01 08:52:18 |
quanxian |
description |
Description
We already keep the sector in the radix tree as part of the exceptional entry. For page faults where we already have an exceptional entry, use this information directly from the radix tree instead of calling into the filesystem to get a block mapping. This should show a measurable performance improvement, which should be reported as motivation for the patches.
Target Kernel:4.17
Target Release: 18.04 |
Description
We already keep the sector in the radix tree as part of the exceptional entry. For page faults where we already have an exceptional entry, use this information directly from the radix tree instead of calling into the filesystem to get a block mapping. This should show a measurable performance improvement, which should be reported as motivation for the patches.
Target Kernel:4.17
Target Release: 18.10 |
|
| 2018-05-01 08:52:27 |
quanxian |
tags |
kernel |
intel-kernel-18.10 kernel |
|
| 2018-05-22 02:27:26 |
quanxian |
description |
Description
We already keep the sector in the radix tree as part of the exceptional entry. For page faults where we already have an exceptional entry, use this information directly from the radix tree instead of calling into the filesystem to get a block mapping. This should show a measurable performance improvement, which should be reported as motivation for the patches.
Target Kernel:4.17
Target Release: 18.10 |
Description
We already keep the sector in the radix tree as part of the exceptional entry. For page faults where we already have an exceptional entry, use this information directly from the radix tree instead of calling into the filesystem to get a block mapping. This should show a measurable performance improvement, which should be reported as motivation for the patches.
Target Kernel:4.19
Target Release: 18.10 |
|
| 2018-07-25 15:59:02 |
Joseph Salisbury |
intel: importance |
Undecided |
Medium |
|
| 2018-07-25 15:59:05 |
Joseph Salisbury |
intel: status |
Incomplete |
Triaged |
|
| 2018-07-25 15:59:18 |
Joseph Salisbury |
intel: assignee |
|
Canonical Kernel Team (canonical-kernel-team) |
|
| 2018-07-25 15:59:24 |
Joseph Salisbury |
tags |
intel-kernel-18.10 kernel |
intel-kernel-18.10 kernel kernel-da-key |
|
| 2018-09-14 02:12:57 |
quanxian |
description |
Description
We already keep the sector in the radix tree as part of the exceptional entry. For page faults where we already have an exceptional entry, use this information directly from the radix tree instead of calling into the filesystem to get a block mapping. This should show a measurable performance improvement, which should be reported as motivation for the patches.
Target Kernel:4.19
Target Release: 18.10 |
Description
We already keep the sector in the radix tree as part of the exceptional entry. For page faults where we already have an exceptional entry, use this information directly from the radix tree instead of calling into the filesystem to get a block mapping. This should show a measurable performance improvement, which should be reported as motivation for the patches.
Target Kernel:TBD
Target Release: 18.10 |
|
| 2018-09-14 02:15:01 |
quanxian |
information type |
Private |
Public |
|
| 2018-10-26 02:50:08 |
quanxian |
description |
Description
We already keep the sector in the radix tree as part of the exceptional entry. For page faults where we already have an exceptional entry, use this information directly from the radix tree instead of calling into the filesystem to get a block mapping. This should show a measurable performance improvement, which should be reported as motivation for the patches.
Target Kernel:TBD
Target Release: 18.10 |
Description
We already keep the sector in the radix tree as part of the exceptional entry. For page faults where we already have an exceptional entry, use this information directly from the radix tree instead of calling into the filesystem to get a block mapping. This should show a measurable performance improvement, which should be reported as motivation for the patches.
Target Kernel:TBD
Target Release: 19.04 |
|
| 2018-10-26 02:50:19 |
quanxian |
tags |
intel-kernel-18.10 kernel kernel-da-key |
intel-kernel-19.04 kernel kernel-da-key |
|
| 2018-10-26 02:50:26 |
quanxian |
bug task added |
|
ubuntu |
|
| 2019-04-04 08:32:22 |
guo xuelian |
information type |
Public |
Private |
|
| 2019-04-04 08:32:39 |
guo xuelian |
information type |
Private |
Public |
|
| 2019-05-06 08:30:24 |
quanxian |
affects |
ubuntu |
linux (Ubuntu) |
|
| 2019-05-06 08:30:41 |
quanxian |
description |
Description
We already keep the sector in the radix tree as part of the exceptional entry. For page faults where we already have an exceptional entry, use this information directly from the radix tree instead of calling into the filesystem to get a block mapping. This should show a measurable performance improvement, which should be reported as motivation for the patches.
Target Kernel:TBD
Target Release: 19.04 |
Description
We already keep the sector in the radix tree as part of the exceptional entry. For page faults where we already have an exceptional entry, use this information directly from the radix tree instead of calling into the filesystem to get a block mapping. This should show a measurable performance improvement, which should be reported as motivation for the patches.
Target Kernel:TBD
Target Release: 19.10 |
|
| 2019-05-06 08:30:49 |
quanxian |
tags |
intel-kernel-19.04 kernel kernel-da-key |
intel-kernel-19.10 kernel kernel-da-key |
|
| 2019-05-06 09:00:07 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2019-05-06 09:00:10 |
Ubuntu Kernel Bot |
tags |
intel-kernel-19.10 kernel kernel-da-key |
eoan intel-kernel-19.10 kernel kernel-da-key |
|
| 2019-06-28 13:01:19 |
quanxian |
intel: status |
Triaged |
Invalid |
|
| 2019-08-28 04:17:25 |
Launchpad Janitor |
linux (Ubuntu): status |
Incomplete |
Expired |
|
