android_system_core/storaged
Tom Cherry 3b4bddc638 Remove liblog's rate limiting
After a few years of being available, there only ended up being one
user of this, so it is clear that logd's duplicate message mechanism
is the favored solution.

The one user of this rate limiting is questionable as is, since due to
the nature of storaged, the mainloop only runs once per minute by
default as is, so there is essentially nothing to be gained by rate
limiting any further.

Test: build
Change-Id: I0610d11efda1ce8b581b939bad11ff295cb2daa6
2019-01-16 10:37:14 -08:00
..
binder/android/os
include
tests
tools
Android.bp Match src paths with aidl package name 2018-09-14 21:27:31 -07:00
EventLogTags.logtags
OWNERS
README.properties
main.cpp
storaged.cpp Remove liblog's rate limiting 2019-01-16 10:37:14 -08:00
storaged.proto
storaged.rc
storaged_diskstats.cpp storaged: change log level for health HAL calls 2018-09-13 09:41:46 -07:00
storaged_info.cpp storaged: emplace recent_perf in load_perf_history_proto 2018-11-20 09:00:05 -08:00
storaged_service.cpp Move system/core/ off NO_ERROR. 2018-10-08 11:15:52 -07:00
storaged_uid_monitor.cpp
storaged_utils.cpp
uid_info.cpp Move system/core/ off NO_ERROR. 2018-10-08 11:15:52 -07:00

README.properties

ro.storaged.event.interval    # interval storaged scans for IO stats, in seconds
ro.storaged.event.perf_check  # check for time spent in event loop, in microseconds
ro.storaged.disk_stats_pub    # interval storaged publish disk stats, in seconds
ro.storaged.uid_io.interval   # interval storaged checks Per UID IO usage, in seconds
ro.storaged.uid_io.threshold  # Per UID IO usage limit, in bytes