All autopkgtests for the newly accepted linux-azure-5.3 (5.3.0-1034.35~18.04.1) 
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/0.7.5-1ubuntu16.9 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-azure-5.3

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
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/1882039

Title:
  The thread level parallelism would be a bottleneck when searching for
  the shared pmd by using hugetlbfs

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  There is performance overhead observed when many threads
  are using hugetlbfs in the database environment.

  [Fix]

  bdfbd98bc018 hugetlbfs: take read_lock on i_mmap for PMD sharing

  The patch improves the locking by using the read lock instead of the
  write lock. And it allows multiple threads searching the suitable shared
  VMA. As there is no modification inside the searching process. The 
  improvement increases the parallelism and decreases the waiting time of
  the other threads.

  [Test]

  The customer stand-up a database with seed data. Then they have a
  loading "driver" which makes a bunch of connections that look like user
  workflows from the database perspective. Finally, the measuring response
  times improvement can be observed for these "users" as well as various
  other metrics at the database level.

  [Regression Potential]

  The modification is only in replacing the write lock to a read one. And 
  there is no modification inside the loop. The regression probability is
  low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882039/+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