From: Loic Dachary <loic@dachary.org>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: SSE extensions detection problem on the current master
Date: Tue, 18 Mar 2014 12:16:48 +0100 [thread overview]
Message-ID: <53282B20.9000508@dachary.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 507 bytes --]
Hi Ceph,
Builds happening after
https://github.com/ceph/ceph/commit/7bc9ade26b5af068318e50cb4d5f7824375dd28f
which was merged yesterday and before the following is merged
https://github.com/ceph/ceph/pull/1489
will produce binaries using SSE extensions on intel processors without checking their availability at runtime, when using erasure coded pools only. I'm not sure how it will fail or when, but it is better to not try ;-)
Cheers
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
reply other threads:[~2014-03-18 11:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=53282B20.9000508@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
/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.