2016-02-10 00:12:00 +01:00
|
|
|
// Copyright (c) 2011-present, Facebook, Inc. All rights reserved.
|
2017-07-16 01:03:42 +02:00
|
|
|
// This source code is licensed under both the GPLv2 (found in the
|
|
|
|
// COPYING file in the root directory) and Apache 2.0 License
|
|
|
|
// (found in the LICENSE.Apache file in the root directory).
|
2014-07-04 01:28:03 +02:00
|
|
|
//
|
|
|
|
#pragma once
|
2017-04-06 04:02:00 +02:00
|
|
|
#include "monitoring/perf_step_timer.h"
|
2014-07-04 01:28:03 +02:00
|
|
|
#include "rocksdb/iostats_context.h"
|
|
|
|
|
cross-platform compatibility improvements
Summary:
We've had a couple CockroachDB users fail to build RocksDB on exotic platforms, so I figured I'd try my hand at solving these issues upstream. The problems stem from a) `USE_SSE=1` being too aggressive about turning on SSE4.2, even on toolchains that don't support SSE4.2 and b) RocksDB attempting to detect support for thread-local storage based on OS, even though it can vary by compiler on the same OS.
See the individual commit messages for details. Regarding SSE support, this PR should change virtually nothing for non-CMake based builds. `make`, `PORTABLE=1 make`, `USE_SSE=1 make`, and `PORTABLE=1 USE_SSE=1 make` function exactly as before, except that SSE support will be automatically disabled when a simple SSE4.2-using test program fails to compile, as it does on OpenBSD. (OpenBSD's ports GCC supports SSE4.2, but its binutils do not, so `__SSE_4_2__` is defined but an SSE4.2-using program will fail to assemble.) A warning is emitted in this case. The CMake build is modified to support the same set of options, except that `USE_SSE` is spelled `FORCE_SSE42` because `USE_SSE` is rather useless now that we can automatically detect SSE support, and I figure changing options in the CMake build is less disruptive than changing the non-CMake build.
I've tested these changes on all the platforms I can get my hands on (macOS, Windows MSVC, Windows MinGW, and OpenBSD) and it all works splendidly. Let me know if there's anything you object to—I obviously don't mean to break any of your build pipelines in the process of fixing ours downstream.
Closes https://github.com/facebook/rocksdb/pull/2199
Differential Revision: D5054042
Pulled By: yiwu-arbug
fbshipit-source-id: 938e1fc665c049c02ae15698e1409155b8e72171
2017-05-15 23:42:32 +02:00
|
|
|
#ifdef ROCKSDB_SUPPORT_THREAD_LOCAL
|
2020-02-20 21:07:53 +01:00
|
|
|
namespace ROCKSDB_NAMESPACE {
|
2017-09-16 02:02:37 +02:00
|
|
|
extern __thread IOStatsContext iostats_context;
|
2020-02-20 21:07:53 +01:00
|
|
|
} // namespace ROCKSDB_NAMESPACE
|
2014-08-28 18:46:05 +02:00
|
|
|
|
2014-07-04 01:28:03 +02:00
|
|
|
// increment a specific counter by the specified value
|
2017-09-16 02:02:37 +02:00
|
|
|
#define IOSTATS_ADD(metric, value) (iostats_context.metric += value)
|
2014-07-04 01:28:03 +02:00
|
|
|
|
|
|
|
// Increase metric value only when it is positive
|
|
|
|
#define IOSTATS_ADD_IF_POSITIVE(metric, value) \
|
|
|
|
if (value > 0) { IOSTATS_ADD(metric, value); }
|
|
|
|
|
|
|
|
// reset a specific counter to zero
|
2017-09-16 02:02:37 +02:00
|
|
|
#define IOSTATS_RESET(metric) (iostats_context.metric = 0)
|
2014-07-04 01:28:03 +02:00
|
|
|
|
|
|
|
// reset all counters to zero
|
2017-09-16 02:02:37 +02:00
|
|
|
#define IOSTATS_RESET_ALL() (iostats_context.Reset())
|
2014-07-04 01:28:03 +02:00
|
|
|
|
2017-09-16 02:02:37 +02:00
|
|
|
#define IOSTATS_SET_THREAD_POOL_ID(value) \
|
|
|
|
(iostats_context.thread_pool_id = value)
|
2014-07-04 01:28:03 +02:00
|
|
|
|
2017-09-16 02:02:37 +02:00
|
|
|
#define IOSTATS_THREAD_POOL_ID() (iostats_context.thread_pool_id)
|
2014-07-04 01:28:03 +02:00
|
|
|
|
2017-09-16 02:02:37 +02:00
|
|
|
#define IOSTATS(metric) (iostats_context.metric)
|
2014-08-28 18:46:05 +02:00
|
|
|
|
2015-06-02 11:07:58 +02:00
|
|
|
// Declare and set start time of the timer
|
2017-09-16 02:02:37 +02:00
|
|
|
#define IOSTATS_TIMER_GUARD(metric) \
|
|
|
|
PerfStepTimer iostats_step_timer_##metric(&(iostats_context.metric)); \
|
2017-06-03 02:12:39 +02:00
|
|
|
iostats_step_timer_##metric.Start();
|
2015-06-02 11:07:58 +02:00
|
|
|
|
2019-01-30 01:23:21 +01:00
|
|
|
// Declare and set start time of the timer
|
2021-01-26 07:07:26 +01:00
|
|
|
#define IOSTATS_CPU_TIMER_GUARD(metric, clock) \
|
2019-01-30 01:23:21 +01:00
|
|
|
PerfStepTimer iostats_step_timer_##metric( \
|
2021-03-15 12:32:24 +01:00
|
|
|
&(iostats_context.metric), clock, true, \
|
2019-01-30 01:23:21 +01:00
|
|
|
PerfLevel::kEnableTimeAndCPUTimeExceptForMutex); \
|
|
|
|
iostats_step_timer_##metric.Start();
|
|
|
|
|
cross-platform compatibility improvements
Summary:
We've had a couple CockroachDB users fail to build RocksDB on exotic platforms, so I figured I'd try my hand at solving these issues upstream. The problems stem from a) `USE_SSE=1` being too aggressive about turning on SSE4.2, even on toolchains that don't support SSE4.2 and b) RocksDB attempting to detect support for thread-local storage based on OS, even though it can vary by compiler on the same OS.
See the individual commit messages for details. Regarding SSE support, this PR should change virtually nothing for non-CMake based builds. `make`, `PORTABLE=1 make`, `USE_SSE=1 make`, and `PORTABLE=1 USE_SSE=1 make` function exactly as before, except that SSE support will be automatically disabled when a simple SSE4.2-using test program fails to compile, as it does on OpenBSD. (OpenBSD's ports GCC supports SSE4.2, but its binutils do not, so `__SSE_4_2__` is defined but an SSE4.2-using program will fail to assemble.) A warning is emitted in this case. The CMake build is modified to support the same set of options, except that `USE_SSE` is spelled `FORCE_SSE42` because `USE_SSE` is rather useless now that we can automatically detect SSE support, and I figure changing options in the CMake build is less disruptive than changing the non-CMake build.
I've tested these changes on all the platforms I can get my hands on (macOS, Windows MSVC, Windows MinGW, and OpenBSD) and it all works splendidly. Let me know if there's anything you object to—I obviously don't mean to break any of your build pipelines in the process of fixing ours downstream.
Closes https://github.com/facebook/rocksdb/pull/2199
Differential Revision: D5054042
Pulled By: yiwu-arbug
fbshipit-source-id: 938e1fc665c049c02ae15698e1409155b8e72171
2017-05-15 23:42:32 +02:00
|
|
|
#else // ROCKSDB_SUPPORT_THREAD_LOCAL
|
2014-08-28 18:46:05 +02:00
|
|
|
|
|
|
|
#define IOSTATS_ADD(metric, value)
|
|
|
|
#define IOSTATS_ADD_IF_POSITIVE(metric, value)
|
|
|
|
#define IOSTATS_RESET(metric)
|
|
|
|
#define IOSTATS_RESET_ALL()
|
|
|
|
#define IOSTATS_SET_THREAD_POOL_ID(value)
|
|
|
|
#define IOSTATS_THREAD_POOL_ID()
|
|
|
|
#define IOSTATS(metric) 0
|
|
|
|
|
2015-06-02 11:07:58 +02:00
|
|
|
#define IOSTATS_TIMER_GUARD(metric)
|
2021-01-26 07:07:26 +01:00
|
|
|
#define IOSTATS_CPU_TIMER_GUARD(metric, clock) static_cast<void>(clock)
|
2015-06-02 11:07:58 +02:00
|
|
|
|
cross-platform compatibility improvements
Summary:
We've had a couple CockroachDB users fail to build RocksDB on exotic platforms, so I figured I'd try my hand at solving these issues upstream. The problems stem from a) `USE_SSE=1` being too aggressive about turning on SSE4.2, even on toolchains that don't support SSE4.2 and b) RocksDB attempting to detect support for thread-local storage based on OS, even though it can vary by compiler on the same OS.
See the individual commit messages for details. Regarding SSE support, this PR should change virtually nothing for non-CMake based builds. `make`, `PORTABLE=1 make`, `USE_SSE=1 make`, and `PORTABLE=1 USE_SSE=1 make` function exactly as before, except that SSE support will be automatically disabled when a simple SSE4.2-using test program fails to compile, as it does on OpenBSD. (OpenBSD's ports GCC supports SSE4.2, but its binutils do not, so `__SSE_4_2__` is defined but an SSE4.2-using program will fail to assemble.) A warning is emitted in this case. The CMake build is modified to support the same set of options, except that `USE_SSE` is spelled `FORCE_SSE42` because `USE_SSE` is rather useless now that we can automatically detect SSE support, and I figure changing options in the CMake build is less disruptive than changing the non-CMake build.
I've tested these changes on all the platforms I can get my hands on (macOS, Windows MSVC, Windows MinGW, and OpenBSD) and it all works splendidly. Let me know if there's anything you object to—I obviously don't mean to break any of your build pipelines in the process of fixing ours downstream.
Closes https://github.com/facebook/rocksdb/pull/2199
Differential Revision: D5054042
Pulled By: yiwu-arbug
fbshipit-source-id: 938e1fc665c049c02ae15698e1409155b8e72171
2017-05-15 23:42:32 +02:00
|
|
|
#endif // ROCKSDB_SUPPORT_THREAD_LOCAL
|