From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stefan Hanreich <s.hanreich@proxmox.com>
Subject: [pve-devel] applied: [PATCH pve-ceph] fix compatibility with CPUs not supporting SSE 4.1 instructions
Date: Tue, 31 Oct 2023 10:52:12 +0100 [thread overview]
Message-ID: <ae28569f-9810-41d7-94f9-9131a29b9d41@proxmox.com> (raw)
In-Reply-To: <20230918154656.2717366-1-s.hanreich@proxmox.com>
On 18/09/2023 17:46, Stefan Hanreich wrote:
> One of our users ran into issues with running Ceph on older CPU
> architectures [1]. This is apparently due to a bug in gcc-12 that
> leads to SSE 4.1 instructions always being executed rather than
> dynamically dispatching functions using those instructions. Those
> binaries then break on older CPUs that do not support this instruction
> set.
>
> I've ran some benchmarks with `rados bench` against our last release
> (18.2.0-pve2) and this new version. The commands were taken from our
> latest Ceph benchmarking paper [2]. The results showed that this patch
> does not lead to performance regressions on newer hardware.
>
> 18.2.0-pve2 this patch
> Read EC 4574.28 4651.95
> Write EC 3739.59 3773.87
> Read Replicated 5345.34 5568.41
> Write Replicated 4123.28 4066.19
> (numbers correspond to bandwidth in MB/s)
>
> [1] https://forum.proxmox.com/threads/proxmox-8-ceph-quincy-monitor-no-longer-working-on-amd-opteron-2427.129613
> [2] https://www.proxmox.com/en/downloads/proxmox-virtual-environment/documentation/proxmox-ve-ceph-benchmark-2020-09
>
> Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
> ---
> ...y-with-CPUs-not-supporting-SSE-4.1-i.patch | 32 +++++++++++++++++++
> patches/series | 1 +
> 2 files changed, 33 insertions(+)
> create mode 100644 patches/0015-fix-compatibility-with-CPUs-not-supporting-SSE-4.1-i.patch
>
>
applied, with a reworded commit message, shifting the blame to the
combination of gf-complete and gcc-12, as the former does some rather
funky stuff too, thanks!
Having this reported to the GCC and/or gf-complete people, ideally
with a reduced example (compiling ceph is a bit overkill ;-)
Using elfx86exts [0] as mentioned in the debian bug [1] should be
enough to ensure your reduced example is still affected and contains
SSE 4.1 instructions.
[0]: https://github.com/pkgw/elfx86exts
[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012935#10
prev parent reply other threads:[~2023-10-31 9:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 15:46 [pve-devel] " Stefan Hanreich
2023-09-18 16:02 ` Dietmar Maurer
2023-09-19 10:06 ` Thomas Lamprecht
2023-10-31 9:52 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ae28569f-9810-41d7-94f9-9131a29b9d41@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.hanreich@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal