84b7ca8d81
The code previously assumed that write() took a non-zero number of clock
ticks. This is mostly true, but can't be guaranteed. Add a check to
avoid crashing if it's 0.
Bug: 233008287
Test: Compile
Change-Id: Idec0052f534dc4abb81a414ca76f6c11f4a4dded
(cherry picked from commit
|
||
---|---|---|
.. | ||
binder/android/os | ||
include | ||
tests | ||
tools | ||
Android.bp | ||
EventLogTags.logtags | ||
main.cpp | ||
OWNERS | ||
README.properties | ||
storaged.cpp | ||
storaged.proto | ||
storaged.rc | ||
storaged_diskstats.cpp | ||
storaged_info.cpp | ||
storaged_service.cpp | ||
storaged_uid_monitor.cpp | ||
storaged_utils.cpp | ||
uid_info.cpp |
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