blob: 33e97d1729e798af2c2f2bbfb16c86e64271789e [file] [log] [blame]
What: /sys/devices/platform/soc/<....>ufshc/manual_gc
Date: April, 2018
Contact: "Jaegeuk Kim" <jaegeuk@google.com>
Description:
Control UFS to give a time for internal Garbage Collections,
given manual_gc_hold seconds.
What: /sys/devices/platform/soc/<....>ufshc/manual_gc_hold
Date: April, 2018
Contact: "Jaegeuk Kim" <jaegeuk@google.com>
Description:
Give the seconds to UFS for internal GCs.
What: /sys/devices/platform/soc/<....>ufshc/slowio_read_us
Date: May, 2018
Contact: "Hyojun Kim" <hyojun@google.com>
Description:
Contains watermark value in micro seconds unit for slow
UFS read I/O logging and counting. Can be updated by writing
value to.
What: /sys/devices/platform/soc/<....>ufshc/slowio_read_cnt
Date: May, 2018
Contact: "Hyojun Kim" <hyojun@google.com>
Description:
Contains the number of UFS read I/O requests which took more
or equal to the defined slow I/O water mark time.
Can be reset by writing any value.
What: /sys/devices/platform/soc/<....>ufshc/slowio_write_us
Date: May, 2018
Contact: "Hyojun Kim" <hyojun@google.com>
Description:
Contains watermark value in micro seconds unit for slow
UFS write I/O logging and counting. Can be updated by writing
value to.
What: /sys/devices/platform/soc/<....>ufshc/slowio_write_cnt
Date: May, 2018
Contact: "Hyojun Kim" <hyojun@google.com>
Description:
Contains the number of UFS write I/O requests which took more
or equal to the defined slow I/O water mark time.
Can be reset by writing any value.
What: /sys/devices/platform/soc/<....>ufshc/slowio_unmap_us
Date: May, 2018
Contact: "Hyojun Kim" <hyojun@google.com>
Description:
Contains watermark value in micro seconds unit for slow
UFS unmap I/O logging and counting. Can be updated by writing
value to.
What: /sys/devices/platform/soc/<....>ufshc/slowio_unmap_cnt
Date: May, 2018
Contact: "Hyojun Kim" <hyojun@google.com>
Description:
Contains the number of UFS unmap I/O requests which took more
or equal to the defined slow I/O water mark time.
Can be reset by writing any value.
What: /sys/devices/platform/soc/<....>ufshc/slowio_sync_us
Date: May, 2018
Contact: "Hyojun Kim" <hyojun@google.com>
Description:
Contains watermark value in micro seconds unit for slow
UFS sync I/O logging and counting. Can be updated by writing
value to.
What: /sys/devices/platform/soc/<....>ufshc/slowio_sync_cnt
Date: May, 2018
Contact: "Hyojun Kim" <hyojun@google.com>
Description:
Contains the number of UFS sync I/O requests which took more
or equal to the defined slow I/O water mark time.
Can be reset by writing any value.
What: /sys/devices/platform/soc/<....>ufshc/impaired/enabled
Date: December, 2018
Contact: "Hyojun Kim" <hyojun@google.com>
Description:
Enable or disable impaired storage emulation.
What: /sys/devices/platform/soc/<....>ufshc/impaired/read_model
Date: December, 2018
Contact: "Hyojun Kim" <hyojun@google.com>
Description:
Degraded UFS performance model is applied for read requests.
It could be set with 'fragftl' or 'none'; the former enables
model based delay emulation and the later disables the feature.
What: /sys/devices/platform/soc/<....>ufshc/impaired/read_delay_percent
Date: December, 2018
Contact: "Hyojun Kim" <hyojun@google.com>
Description:
This knob can be used to control target delay for UFS read requests.
It receives a precentage value, and the default value is 100, which means
no change. When 200 is written, the target latency with delay will be
twice of an input latency, which is either the actual latency or a latency
chosen by the degraded performance model when fragmented ftl emulation
feature is enabled.
What: /sys/devices/platform/soc/<....>ufshc/impaired/read_delay_us
Date: December, 2018
Contact: "Hyojun Kim" <hyojun@google.com>
Description:
This knob is used to control target delay for UFS read requsts.
For each read request, this value will be added to the target delay.
For instance, when 200 is set, all read requests will be delayed
by 200 microseconds. The default value is 0, which means no delay.
What: /sys/devices/platform/soc/<....>ufshc/impaired/write_model
Date: December, 2018
Contact: "Hyojun Kim" <hyojun@google.com>
Description:
Degraded UFS performance model is applied for write requests.
It could be set with 'fragftl' or 'none'; the former enables
model based delay emulation and the later disables the feature.
What: /sys/devices/platform/soc/<....>ufshc/impaired/write_delay_percent
Date: December, 2018
Contact: "Hyojun Kim" <hyojun@google.com>
Description:
This knob can be used to control target delay for UFS write requests.
It receives a precentage value, and the default value is 100, which means
no change. When 200 is written, the target latency with delay will be
twice of an input latency, which is either the actual latency or a latency
chosen by the degraded performance model when fragmented ftl emulation
feature is enabled.
What: /sys/devices/platform/soc/<....>ufshc/impaired/write_delay_us
Date: December, 2018
Contact: "Hyojun Kim" <hyojun@google.com>
Description:
This knob is used to control target delay for UFS write requsts.
For each write request, this value will be added to the target delay.
For instance, when 200 is set, all write requests will be delayed
by 200 microseconds. The default value is 0, which means no delay.
What: /sys/devices/platform/soc/<....>ufshc/impaired/read_max_delayed_us
Date: December, 2018
Contact: "Hyojun Kim" <hyojun@google.com>
Description:
Maximum read request latency can be set by this entry. For instance,
when 1000 is set to this entry, the emulated read latency will not
be bigger than 1ms.
Default value is 0, which means no limitation.
What: /sys/devices/platform/soc/<....>ufshc/impaired/read_skip_delay_cnt
Date: December, 2018
Contact: "Hyojun Kim" <hyojun@google.com>
Description:
This knob can be used to control delay emulation frequency.
When the default 0 is set, all read requests are delayed.
When 1 is written, every other read request is delayed.
What: /sys/devices/platform/soc/<....>ufshc/impaired/write_max_delayed_us
Date: December, 2018
Contact: "Hyojun Kim" <hyojun@google.com>
Description:
Maximum write request latency can be set by this entry. For instance,
when 1000 is set to this entry, the emulated write latency will not
be bigger than 1ms.
Default value is 0, which means no limitation.
What: /sys/devices/platform/soc/<....>ufshc/impaired/write_skip_delay_cnt
Date: December, 2018
Contact: "Hyojun Kim" <hyojun@google.com>
Description:
This knob can be used to control delay emulation frequency.
When the default 0 is set, all write requests are delayed.
When 1 is written, every other write request is delayed.
What: /sys/devices/platform/soc/<....>ufshc/impaired/read_total_cnt
Date: December, 2018
Contact: "Hyojun Kim" <hyojun@google.com>
Description:
Total number of read requests can be checked by reading this entry.
Can be reset together with all other statistics entries when
any value is written to.
What: /sys/devices/platform/soc/<....>ufshc/impaired/read_total_original_us
Date: December, 2018
Contact: "Hyojun Kim" <hyojun@google.com>
Description:
Aggregated original read latencies without added delay can be checked
by reading this entry.
Can be reset together with all other statistics entries when
any value is written to.
What: /sys/devices/platform/soc/<....>ufshc/impaired/read_total_delayed_us
Date: December, 2018
Contact: "Hyojun Kim" <hyojun@google.com>
Description:
Aggregated read latencies with delay emulation can be checked
by reading this entry.
Can be reset together with all other statistics entries when
any value is written to.
What: /sys/devices/platform/soc/<....>ufshc/impaired/write_total_cnt
Date: December, 2018
Contact: "Hyojun Kim" <hyojun@google.com>
Description:
Total number of write requests can be checked by reading this entry.
Can be reset together with all other statistics entries when
any value is written to.
What: /sys/devices/platform/soc/<....>ufshc/impaired/write_total_original_us
Date: December, 2018
Contact: "Hyojun Kim" <hyojun@google.com>
Description:
Aggregated original write latencies without added delay can be checked
by reading this entry.
Can be reset together with all other statistics entries when
any value is written to.
What: /sys/devices/platform/soc/<....>ufshc/impaired/write_total_delayed_us
Date: December, 2018
Contact: "Hyojun Kim" <hyojun@google.com>
Description:
Aggregated write latencies with delay emulation can be checked
by reading this entry.
Can be reset together with all other statistics entries when
any value is written to.
What: /sys/devices/platform/soc/<....>ufshc/impaired/read_max_delay_us
Date: December, 2018
Contact: "Hyojun Kim" <hyojun@google.com>
Description:
Maximum read delay in microseconds, targeted by delay emulation,
can be checked by reading this entry.
Can be reset together with all other statistics entries when
any value is written to.
What: /sys/devices/platform/soc/<....>ufshc/impaired/read_max_delay_error_us
Date: December, 2018
Contact: "Hyojun Kim" <hyojun@google.com>
Description:
Added delay might be different from the intended delay value.
By reading this entry, observed maximum read delay error value can be
checked in microsecond unit.
Can be reset together with all other statistics entries when
any value is written to.
What: /sys/devices/platform/soc/<....>ufshc/impaired/read_total_delay_error_us
Date: December, 2018
Contact: "Hyojun Kim" <hyojun@google.com>
Description:
Added delay might be different from the intended delay value.
For all delayed read requests, the additional delay value than intended delay
is aggrated to this entry.
Can be reset together with all other statistics entries when
any value is written to.
What: /sys/devices/platform/soc/<....>ufshc/impaired/write_max_delay_us
Date: December, 2018
Contact: "Hyojun Kim" <hyojun@google.com>
Description:
Maximum write delay in microseconds, targeted by delay emulation,
can be checked by reading this entry.
Can be reset together with all other statistics entries when
any value is written to.
What: /sys/devices/platform/soc/<....>ufshc/impaired/write_max_delay_error_us
Date: December, 2018
Contact: "Hyojun Kim" <hyojun@google.com>
Description:
Added delay might be different from the intended delay value.
By reading this entry, observed maximum write delay error value can be
checked in microsecond unit.
Can be reset together with all other statistics entries when
any value is written to.
What: /sys/devices/platform/soc/<....>ufshc/impaired/write_total_delay_error_us
Date: December, 2018
Contact: "Hyojun Kim" <hyojun@google.com>
Description:
Added delay might be different from the intended delay value.
For all delayed write requests, the additional delay value than intended delay
is aggrated to this entry.
Can be reset together with all other statistics entries when
any value is written to.