| /openbmc/bmcweb/redfish-core/include/generated/enums/ |
| H A D | triggers.hpp | 29 Increasing, enumerator
37 Increasing, enumerator
69 {ThresholdActivation::Increasing, "Increasing"},
77 {DirectionOfCrossingEnum::Increasing, "Increasing"},
|
| H A D | sensor.hpp | 37 Increasing, enumerator
114 {ThresholdActivation::Increasing, "Increasing"},
|
| /openbmc/telemetry/tests/src/ |
| H A D | test_numeric_threshold.cpp | 52 makeThreshold(0ms, numeric::Direction::increasing, 90.0, in SetUp()
78 numeric::Type::upperCritical, 0, numeric::Direction::increasing, 90.0); in TEST_F()
257 .Direction(numeric::Direction::increasing)
263 .Direction(numeric::Direction::increasing)
269 .Direction(numeric::Direction::increasing)
275 .Direction(numeric::Direction::increasing)
341 .Direction(numeric::Direction::increasing)
347 .Direction(numeric::Direction::increasing)
384 .Direction(numeric::Direction::increasing)
391 .Direction(numeric::Direction::increasing)
[all …]
|
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 075.out | 24 …en device TEST_DIR/simple-pattern.cloop: image requires too many offsets, try increasing block size
26 == refuse images with non-monotonically increasing offsets ==
27 qemu-io: can't open device TEST_DIR/simple-pattern.cloop: offsets not monotonically increasing at i…
|
| /openbmc/linux/Documentation/devicetree/bindings/scsi/ |
| H A D | hisilicon-sas.txt | 31 (broadcast, phyup, and abnormal) in increasing order.
34 The interrupts are ordered in increasing order.
47 interrupt. The interrupts are ordered in increasing
51 increasing order.
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/mellanox/mlx5/ |
| H A D | counters.rst | 919 on a physical port. If this counter is increasing, it implies that the
926 size on a physical port. If this counter is increasing, it implies that
946 this counter is increasing, it implies that the network is congested and
952 this counter is increasing, it implies that the NIC is congested and
963 physical port. If this counter is increasing, it implies that the adapter
980 than 64 bytes on a physical port. If this counter is increasing, it
988 increasing, it implies that the peer connected to the adapter has a
1048 case this counter is increasing it may imply on port flapping. You may
1107 interface. If this counter is increasing, it implies that the link
1116 (RS/FC). If this counter is increasing, it implies that the link between
[all …]
|
| /openbmc/telemetry/src/ |
| H A D | numeric_threshold.cpp | 68 crossedIncreasing = prevDirection == numeric::Direction::increasing && in sensorUpdated()
78 (direction == numeric::Direction::increasing && crossedIncreasing) || in sensorUpdated()
85 prevDirection = value > prevValue ? numeric::Direction::increasing in sensorUpdated()
|
| /openbmc/linux/drivers/media/test-drivers/vidtv/ |
| H A D | vidtv_common.c | 45 …pr_err_ratelimited("overflow detected, skipping. Try increasing the buffer size. Needed %zu, had %… in vidtv_memcpy()
81 …pr_err_ratelimited("overflow detected, skipping. Try increasing the buffer size. Needed %zu, had %… in vidtv_memset()
|
| /openbmc/telemetry/src/types/ |
| H A D | trigger_types.hpp | 81 increasing enumerator
105 "xyz.openbmc_project.Telemetry.Trigger.Direction.Increasing",
106 Direction::increasing)};
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/ivytown/ |
| H A D | uncore-interconnect.json | 764 …onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. Th…
772 …onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. Th…
781 …onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. Th…
790 …onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. Th…
799 …onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. Th…
808 …onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. Th…
817 …onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. Th…
826 …onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. Th…
835 …onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. Th…
844 …onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. Th…
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | Triggers.v1_4_0.json | 37 "Increasing",
42 …"Increasing": "A trigger condition is met when the metric value crosses the trigger value while in… string
253 "Increasing",
262 "Increasing": "Value increases above the threshold." string
267 …"Either": "This threshold is activated when either the `Increasing` or `Decreasing` conditions are…
268 …"Increasing": "This threshold is activated when the reading changes from a value lower than the th… string
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | Triggers.v1_4_0.json | 37 "Increasing",
42 …"Increasing": "A trigger condition is met when the metric value crosses the trigger value while in… string
253 "Increasing",
262 "Increasing": "Value increases above the threshold." string
267 …"Either": "This threshold is activated when either the `Increasing` or `Decreasing` conditions are…
268 …"Increasing": "This threshold is activated when the reading changes from a value lower than the th… string
|
| /openbmc/linux/drivers/gpu/drm/vmwgfx/ |
| H A D | vmwgfx_gmrid_manager.c | 88 DRM_WARN("vmwgfx: mob memory overflow. Consider increasing guest RAM and graphicsMemory.\n"); in vmw_gmrid_man_get_node()
89 …vmw_host_printf("vmwgfx, warning: mob memory overflow. Consider increasing guest RAM and graphicsM… in vmw_gmrid_man_get_node()
97 DRM_WARN("vmwgfx: increasing guest mob limits to %u kB.\n", in vmw_gmrid_man_get_node()
|
| /openbmc/linux/Documentation/block/ |
| H A D | deadline-iosched.rst | 36 write) which are serviced in increasing sector order. To limit extra seeking,
42 a value of 1 yields first-come first-served behaviour). Increasing fifo_batch
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | speeding-up-build.rst | 10 If you have multiple CPUs, you might try increasing the default values
51 thus increasing the build performance.
|
| H A D | init-manager.rst | 43 therefore increasing the total system boot time. systemd also substantially
118 increasing levels of complexity and functionality:
|
| /openbmc/linux/drivers/gpu/drm/arm/display/komeda/ |
| H A D | komeda_kms.c | 122 /* Considering the list sequence is zpos increasing, so if list is empty in komeda_plane_state_list_add()
131 /* Build the list by zpos increasing */ in komeda_plane_state_list_add()
176 /* Build a list by zpos increasing */ in komeda_crtc_normalize_zpos()
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/intel/ |
| H A D | e1000.rst | 193 by the driver. Increasing this value allows the driver to buffer more
214 properly tuned for specific network traffic. Increasing this value adds
265 Increasing this value allows the driver to queue more transmits. Each
414 environments. If this is observed, increasing the application's socket buffer
415 size and/or increasing the /proc/sys/net/ipv4/tcp_*mem entry values may help.
|
| /openbmc/linux/arch/arm64/lib/ |
| H A D | copy_template.S | 52 * Copy the leading memory data from src to dst in an increasing
101 * memory in an increasing address order,rather than to load/store 16
|
| /openbmc/qemu/docs/ |
| H A D | qcow2-cache.txt | 141 memory as possible to the L2 cache before increasing the refcount
149 accessed sequentially (even during random guest I/O) so increasing the
152 to think about increasing the cache size if you use them heavily).
|
| /openbmc/linux/drivers/media/dvb-frontends/ |
| H A D | a8293.h | 21 * @volt_slew_nanos_per_mv: Slew rate when increasing LNB voltage,
|
| /openbmc/linux/Documentation/devicetree/bindings/mmc/ |
| H A D | fsl-imx-esdhc.yaml | 137 Specify the increasing delay cell steps in tuning procedure.
138 The uSDHC use one delay cell as default increasing step to do tuning process.
|
| /openbmc/linux/Documentation/devicetree/bindings/cpufreq/ |
| H A D | cpufreq-spear.txt | 10 increasing order.
|
| /openbmc/openbmc/meta-ibm/recipes-phosphor/pldm/ |
| H A D | pldm_%.bbappend | 12 #so increasing that to 10 seconds here.IBMs custom firmware stack can tolerate
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/jaketown/ |
| H A D | uncore-power.json | 285 …ed by the transition. This event is calculated by or'ing together the increasing and decreasing e…
297 "BriefDescription": "Cycles Increasing Voltage",
301 …"PublicDescription": "Counts the number of cycles when the system is increasing voltage. There is…
|