[Bug 1803077] Re: libatlas not using vector instructions - large performance impact
*** This bug is a duplicate of bug 1814796 *** https://bugs.launchpad.net/bugs/1814796 Changing to Fix Committed because LP 1814796 got Fix Committed - otherwise this is not reflected in IBM's bugzilla. ** Changed in: atlas (Ubuntu) Status: New => Fix Released ** Changed in: ubuntu-z-systems Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803077 Title: libatlas not using vector instructions - large performance impact To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1803077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803077] Re: libatlas not using vector instructions - large performance impact
*** This bug is a duplicate of bug 1814796 *** https://bugs.launchpad.net/bugs/1814796 ** This bug has been marked a duplicate of private bug 1814796 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803077 Title: libatlas not using vector instructions - large performance impact To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1803077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803077] Re: libatlas not using vector instructions - large performance impact
So, I'm expecting for you to provide tarballs similar to: $ ls -latr debian/archdefs/s390x/*.bz2 -rw-r--r-- 1 xnox xnox 7191 Feb 5 15:42 debian/archdefs/s390x/IBMz964.tar.bz2 -rw-r--r-- 1 xnox xnox 7835 Feb 5 15:42 debian/archdefs/s390x/IBMz1264.tar.bz2 but for z13, and z14. Also please check the IBMz1264.tar.bz2 tarball if you can or want to change the performance there. If there are any additional patches required to cherrypick from upstream, please point them out. And any compiler flags. For the tuned builds, we can use things like -march=z13 -O3 and so on. if that results in better performance. For bonus points, you can also work on changing the debian/rules to execute the builds multiple times in separate build directories, but it's probably something quicker for me to hack on, once you have the compiler flags / config options / tuning tarballs done. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803077 Title: libatlas not using vector instructions - large performance impact To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1803077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803077] Re: libatlas not using vector instructions - large performance impact
Note that DEB_BUILD_OPTIONS=custom builds are not something that is suitable to run on our buildds and to ship in the archive for everyone. As the package name clash there, and the build would be for the buildd, rather than for a particular tuning level. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803077 Title: libatlas not using vector instructions - large performance impact To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1803077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803077] Re: libatlas not using vector instructions - large performance impact
"All the infrastructure is in place for many years." the runtime dirs, and compiling - yes; the debian packaging however will need changes to build library multiple times and ship it in the debs, that is not done. We do not have z14; and we would not want to subject our machines to retuning for z13 every time - plus i'm not sure if it will retune successfully on our builders, as we run builders as overcommitted KVM instances. Thus we will need proper tuning files for z13 and z14. Ideally for zEC12 as well, for us to integrate tuned builds. And we don't have capacity to create such tuning files due to lack of access to zEC12 or z14 machines. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803077 Title: libatlas not using vector instructions - large performance impact To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1803077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803077] Re: libatlas not using vector instructions - large performance impact
** Changed in: ubuntu-z-systems Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803077 Title: libatlas not using vector instructions - large performance impact To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1803077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803077] Re: libatlas not using vector instructions - large performance impact
Hi, I'm looking through the atlas code. In 2017, I did contribute changes to packaging to compile atlas with the ARCHS set to z12 on ubuntu (up from z9, and provided the matching archdefs). Looking at the upstream code I do not see any z13 or z14 specific code in atlas - are there any? do we need to upgrade atlas? Is this a request to simply compile the library with `-march=zEC12 -mtune=z14` options? Ideally, we would want to avoid providing three builds for each of the -march=zEC12, -march=z13, -march=z14. Ideally, we would have a single `fat` binary that does runtime detection and does utilize the best available vectorization it can; with explicit code changes or by utilizing automatic compiler function multi- versioning. I.e. many other libraries on s390x and other architectures do runtime detection to exploit NEO, Altivec, AVX2, etc, rather than provide separate builds. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803077 Title: libatlas not using vector instructions - large performance impact To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1803077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803077] Re: libatlas not using vector instructions - large performance impact
** Changed in: atlas (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Dimitri John Ledkov (xnox) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803077 Title: libatlas not using vector instructions - large performance impact To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1803077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803077] Re: libatlas not using vector instructions - large performance impact
Canonical focuses on having a single library build for each architecture in it's archive, containing all possible optimizations (LP 1702917, #4). If a separate z13 optimized library is desired it needs to be placed in a PPA - for example. I think that optimizations should be ideally addressed in the upstream code - for example with (#ifndef) approaches like HW_CAPS or with S390_ALTERNATIVE macros. Any thoughts and opinions? ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803077 Title: libatlas not using vector instructions - large performance impact To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1803077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803077] Re: libatlas not using vector instructions - large performance impact
** Changed in: ubuntu-z-systems Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803077 Title: libatlas not using vector instructions - large performance impact To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1803077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803077] Re: libatlas not using vector instructions - large performance impact
** Tags added: universe ** Also affects: ubuntu-z-systems Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803077 Title: libatlas not using vector instructions - large performance impact To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1803077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803077] Re: libatlas not using vector instructions - large performance impact
** Package changed: linux (Ubuntu) => atlas (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803077 Title: libatlas not using vector instructions - large performance impact To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/atlas/+bug/1803077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803077] Re: libatlas not using vector instructions - large performance impact
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin1804 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803077 Title: libatlas not using vector instructions - large performance impact To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
