Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (356d71e0) · Commits · e / devices / android_kernel_fairphone_FP5

Documentation/ABI/obsolete/sysfs-class-dax

0 → 100644

+22 −0

Original line number	Diff line number	Diff line
		What: /sys/class/dax/
		Date: May, 2016
		KernelVersion: v4.7
		Contact: linux-nvdimm@lists.01.org
		Description: Device DAX is the device-centric analogue of Filesystem
		DAX (CONFIG_FS_DAX). It allows memory ranges to be
		allocated and mapped without need of an intervening file
		system. Device DAX is strict, precise and predictable.
		Specifically this interface:

		1/ Guarantees fault granularity with respect to a given
		page size (pte, pmd, or pud) set at configuration time.

		2/ Enforces deterministic behavior by being strict about
		what fault scenarios are supported.

		The /sys/class/dax/ interface enumerates all the
		device-dax instances in the system. The ABI is
		deprecated and will be removed after 2020. It is
		replaced with the DAX bus interface /sys/bus/dax/ where
		device-dax instances can be found under
		/sys/bus/dax/devices/

+7 −0

Original line number	Diff line number	Diff line
		@@ -86,6 +86,13 @@ Description:
		The unit size is one block, now only support configuring in range
		of [1, 512].

		What: /sys/fs/f2fs/<disk>/umount_discard_timeout
		Date: January 2019
		Contact: "Jaegeuk Kim" <jaegeuk@kernel.org>
		Description:
		Set timeout to issue discard commands during umount.
		Default: 5 secs

		What: /sys/fs/f2fs/<disk>/max_victim_search
		Date: January 2014
		Contact: "Jaegeuk Kim" <jaegeuk.kim@samsung.com>

+3 −0

Original line number	Diff line number	Diff line
		@@ -756,3 +756,6 @@ These currently include:
		The cache mode for raid5. raid5 could include an extra disk for
		caching. The mode can be "write-throuth" and "write-back". The
		default is "write-through".

		ppl_write_hint
		NVMe stream ID to be set for each PPL write request.

+2 −2

Original line number	Diff line number	Diff line
		@@ -6,7 +6,7 @@ TL;DR summary
		* Use only NEON instructions, or VFP instructions that don't rely on support
		code
		* Isolate your NEON code in a separate compilation unit, and compile it with
		'-mfpu=neon -mfloat-abi=softfp'
		'-march=armv7-a -mfpu=neon -mfloat-abi=softfp'
		* Put kernel_neon_begin() and kernel_neon_end() calls around the calls into your
		NEON code
		* Don't sleep in your NEON code, and be aware that it will be executed with
		@@ -87,7 +87,7 @@ instructions appearing in unexpected places if no special care is taken.
		Therefore, the recommended and only supported way of using NEON/VFP in the
		kernel is by adhering to the following rules:
		* isolate the NEON code in a separate compilation unit and compile it with
		'-mfpu=neon -mfloat-abi=softfp';
		'-march=armv7-a -mfpu=neon -mfloat-abi=softfp';
		* issue the calls to kernel_neon_begin(), kernel_neon_end() as well as the calls
		into the unit containing the NEON code from a compilation unit which is not
		built with the GCC flag '-mfpu=neon' set.

+0 −2