Merge "Merge android-4.9.106 (8b94b87) into msm-4.9" (696d37fc) · Commits · e / devices / android_kernel_fairphone_FP3

Documentation/ABI/testing/sysfs-fs-f2fs

+1 −0

Original line number	Diff line number	Diff line
		@@ -101,6 +101,7 @@ Date: February 2015
		Contact: "Jaegeuk Kim" <jaegeuk@kernel.org>
		Description:
		Controls the trimming rate in batch mode.
		<deprecated>

		What: /sys/fs/f2fs/<disk>/cp_interval
		Date: October 2015

+5 −3

Original line number	Diff line number	Diff line
		@@ -112,9 +112,11 @@ $low_water_mark is expressed in blocks of size $data_block_size. If
		free space on the data device drops below this level then a dm event
		will be triggered which a userspace daemon should catch allowing it to
		extend the pool device. Only one such event will be sent.
		Resuming a device with a new table itself triggers an event so the
		userspace daemon can use this to detect a situation where a new table
		already exceeds the threshold.

		No special event is triggered if a just resumed device's free space is below
		the low water mark. However, resuming a device always triggers an
		event; a userspace daemon should verify that free space exceeds the low
		water mark when handling this event.

		A low water mark for the metadata device is maintained in the kernel and
		will trigger a dm event if free space on the metadata device drops below

+5 −1

Original line number	Diff line number	Diff line
		@@ -11,7 +11,11 @@ Required properties:
		interrupts.

		Optional properties:
		- clocks: Optional reference to the clock used by the XOR engine.
		- clocks: Optional reference to the clocks used by the XOR engine.
		- clock-names: mandatory if there is a second clock, in this case the
		name must be "core" for the first clock and "reg" for the second
		one


		Example:

+9 −7

Original line number	Diff line number	Diff line
		@@ -179,13 +179,15 @@ whint_mode=%s Control which write hints are passed down to block
		passes down hints with its policy.
		alloc_mode=%s Adjust block allocation policy, which supports "reuse"
		and "default".
		fsync_mode=%s Control the policy of fsync. Currently supports "posix"
		and "strict". In "posix" mode, which is default, fsync
		will follow POSIX semantics and does a light operation
		to improve the filesystem performance. In "strict" mode,
		fsync will be heavy and behaves in line with xfs, ext4
		and btrfs, where xfstest generic/342 will pass, but the
		performance will regress.
		fsync_mode=%s Control the policy of fsync. Currently supports "posix",
		"strict", and "nobarrier". In "posix" mode, which is
		default, fsync will follow POSIX semantics and does a
		light operation to improve the filesystem performance.
		In "strict" mode, fsync will be heavy and behaves in line
		with xfs, ext4 and btrfs, where xfstest generic/342 will
		pass, but the performance will regress. "nobarrier" is
		based on "posix", but doesn't issue flush command for
		non-atomic files likewise "nobarrier" mount option.
		test_dummy_encryption Enable dummy encryption, which provides a fake fscrypt
		context. The fake fscrypt context is used by xfstests.

+1 −1