Have each timestamp know whether it's coarse or fine. Print six figures
for fine stamps and three for coarse.
Signed-off-by: Adam C. Emerson <aemerson@redhat.com>
When notified by a config observer, the config lock is already held,
create a _get_val template to manipulate newstyle options when
notified.
Signed-off-by: Adam C. Emerson <aemerson@redhat.com>
We create a new time type to support using coarse timestamps (for
performance) by default while still allowing the user to switch to
fine timestamps.
Signed-off-by: Adam C. Emerson <aemerson@redhat.com>
mgr: common interface for TSDB modules
Reviewed-by: My Do <mhdo@umich.edu>
Reviewed-by: Jan Fajerski <jfajerski@suse.com>
Reviewed-by: John Spray <john.spray@redhat.com>
* refs/remotes/upstream/pull/16036/head:
mds: improve cap min/max ratio descriptions
mds: fix whitespace
mds: cap client recall to min caps per client
mds: fix conf types
mds: fix whitespace
doc/cephfs: add client min cache and max cache ratio describe
mds: adding tunable features for caps_per_client
Reviewed-by: Patrick Donnelly <pdonnell@redhat.com>
Reviewed-by: Zheng Yan <zyan@redhat.com>
Add _interfaces option to constrain the choice of IPs in the network
list to those on interfaces matching the provided list of interface names.
The _interfaces options only work in concert with the _network options,
so you must also specify a list of networks if you want to use a specific
interface, e.g., by specifying a broad network like "::" or "0.0.0.0/0".
Signed-off-by: Sage Weil <sage@redhat.com>
If an (optional) preemption context is provided, use that to preempt
and existing reservation and grant a higher-priority one.
Signed-off-by: Sage Weil <sage@redhat.com>
This awkwardly involves re-ordering some definitions
in perf_counters.h in order to refer to the prio
names defined in PerfCountersBuilder.
Signed-off-by: John Spray <john.spray@redhat.com>
Let the caller set a priority as the defaul, to enable them
to create a bunch at a given priority. This is just a
convenience.
Signed-off-by: John Spray <john.spray@redhat.com>
Using PRIO_USEFUL as the threshold for what goes into
time series databases. I'm claiming that we have
more "useful" counters than fit on the screen,
so daemonperf's "a screen's worth" threshold
should be at the "interesting" level.
Signed-off-by: John Spray <john.spray@redhat.com>
Especially since we're just pushing things in from the end. The linked
list has more overhead, is slower, and adds no capability.
Signed-off-by: Adam C. Emerson <aemerson@redhat.com>
Sometimes we need to raise or lower the value of "max_caps_per_client" and
"min_caps_per_client" to improve recall_client_state efficiency
Signed-off-by: ren.huanwen <ren.huanwen@zte.com.cn>
to avoid problems when admin sets system clock.
see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53901 for the reason
why we cannot use atomic<time_point>.
Signed-off-by: Kefu Chai <kchai@redhat.com>
Signed-off-by: Xinze Chi <xinze@xsky.com>
* refs/remotes/upstream/pull/17791/head:
client: set client_try_dentry_invalidate to false by default
Reviewed-by: Patrick Donnelly <pdonnell@redhat.com>
