<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/fs/f2fs/sysfs.c, branch linux-6.10.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-6.10.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-6.10.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2024-10-10T10:00:45Z</updated>
<entry>
<title>f2fs: introduce migration_window_granularity</title>
<updated>2024-10-10T10:00:45Z</updated>
<author>
<name>Daeho Jeong</name>
</author>
<published>2024-09-09T22:19:41Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=31a6f6f44c670ca6356a1ef0041f0a71d9428457'/>
<id>urn:sha1:31a6f6f44c670ca6356a1ef0041f0a71d9428457</id>
<content type='text'>
[ Upstream commit 8c890c4c60342719526520133fb1b6f69f196ab8 ]

We can control the scanning window granularity for GC migration. For
more frequent scanning and GC on zoned devices, we need a fine grained
control knob for it.

Signed-off-by: Daeho Jeong &lt;daehojeong@google.com&gt;
Reviewed-by: Chao Yu &lt;chao@kernel.org&gt;
Signed-off-by: Jaegeuk Kim &lt;jaegeuk@kernel.org&gt;
Stable-dep-of: 5cc69a27abfa ("f2fs: forcibly migrate to secure space for zoned device file pinning")
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>f2fs: add write priority option based on zone UFS</title>
<updated>2024-10-10T10:00:44Z</updated>
<author>
<name>Liao Yuanhong</name>
</author>
<published>2024-07-15T12:34:51Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d26056f9f2b8d9f02493fbdedeed026ee6b75435'/>
<id>urn:sha1:d26056f9f2b8d9f02493fbdedeed026ee6b75435</id>
<content type='text'>
[ Upstream commit 8444ce524947daf441546b5b3a0c418706dade35 ]

Currently, we are using a mix of traditional UFS and zone UFS to support
some functionalities that cannot be achieved on zone UFS alone. However,
there are some issues with this approach. There exists a significant
performance difference between traditional UFS and zone UFS. Under normal
usage, we prioritize writes to zone UFS. However, in critical conditions
(such as when the entire UFS is almost full), we cannot determine whether
data will be written to traditional UFS or zone UFS. This can lead to
significant performance fluctuations, which is not conducive to
development and testing. To address this, we have added an option
zlu_io_enable under sys with the following three modes:
1) zlu_io_enable == 0:Normal mode, prioritize writing to zone UFS;
2) zlu_io_enable == 1:Zone UFS only mode, only allow writing to zone UFS;
3) zlu_io_enable == 2:Traditional UFS priority mode, prioritize writing to
traditional UFS.

Signed-off-by: Liao Yuanhong &lt;liaoyuanhong@vivo.com&gt;
Signed-off-by: Wu Bo &lt;bo.wu@vivo.com&gt;
Reviewed-by: Chao Yu &lt;chao@kernel.org&gt;
Signed-off-by: Jaegeuk Kim &lt;jaegeuk@kernel.org&gt;
Stable-dep-of: 65a6ce4726c2 ("f2fs: fix to don't panic system for no free segment fault injection")
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>f2fs: check validation of fault attrs in f2fs_build_fault_attr()</title>
<updated>2024-05-09T01:04:46Z</updated>
<author>
<name>Chao Yu</name>
</author>
<published>2024-05-07T03:38:47Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=4ed886b187f47447ad559619c48c086f432d2b77'/>
<id>urn:sha1:4ed886b187f47447ad559619c48c086f432d2b77</id>
<content type='text'>
- It missed to check validation of fault attrs in parse_options(),
let's fix to add check condition in f2fs_build_fault_attr().
- Use f2fs_build_fault_attr() in __sbi_store() to clean up code.

Signed-off-by: Chao Yu &lt;chao@kernel.org&gt;
Signed-off-by: Jaegeuk Kim &lt;jaegeuk@kernel.org&gt;
</content>
</entry>
<entry>
<title>f2fs: fix to limit gc_pin_file_threshold</title>
<updated>2024-05-09T01:03:44Z</updated>
<author>
<name>Chao Yu</name>
</author>
<published>2024-05-06T10:45:38Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c521a6ab4ad75fe0755f4cd923a84e1289153aa2'/>
<id>urn:sha1:c521a6ab4ad75fe0755f4cd923a84e1289153aa2</id>
<content type='text'>
type of f2fs_inode.i_gc_failures, f2fs_inode_info.i_gc_failures, and
f2fs_sb_info.gc_pin_file_threshold is __le16, unsigned int, and u64,
so it will cause truncation during comparison and persistence.

Unifying variable of these three variables to unsigned short, and
add an upper boundary limitation for gc_pin_file_threshold.

Signed-off-by: Chao Yu &lt;chao@kernel.org&gt;
Signed-off-by: Jaegeuk Kim &lt;jaegeuk@kernel.org&gt;
</content>
</entry>
<entry>
<title>f2fs: add a proc entry show disk layout</title>
<updated>2024-03-06T17:43:26Z</updated>
<author>
<name>Jaegeuk Kim</name>
</author>
<published>2024-03-04T23:16:56Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f238eff95f485b9e8a1b1a8d4602e8e9d0ae331d'/>
<id>urn:sha1:f238eff95f485b9e8a1b1a8d4602e8e9d0ae331d</id>
<content type='text'>
This patch adds the disk map of block address ranges configured by multiple
partitions.

Reviewed-by: Chao Yu &lt;chao@kernel.org&gt;
Signed-off-by: Jaegeuk Kim &lt;jaegeuk@kernel.org&gt;
</content>
</entry>
<entry>
<title>f2fs: introduce SEGS_TO_BLKS/BLKS_TO_SEGS for cleanup</title>
<updated>2024-03-04T18:18:26Z</updated>
<author>
<name>Chao Yu</name>
</author>
<published>2024-03-04T03:28:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=45809cd3bdac8743f08e42a32121e035aee69d88'/>
<id>urn:sha1:45809cd3bdac8743f08e42a32121e035aee69d88</id>
<content type='text'>
Just cleanup, no functional change.

Signed-off-by: Chao Yu &lt;chao@kernel.org&gt;
Signed-off-by: Jaegeuk Kim &lt;jaegeuk@kernel.org&gt;
</content>
</entry>
<entry>
<title>f2fs: use BLKS_PER_SEG, BLKS_PER_SEC, and SEGS_PER_SEC</title>
<updated>2024-02-27T17:41:12Z</updated>
<author>
<name>Jaegeuk Kim</name>
</author>
<published>2024-02-06T21:56:27Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a60108f7dfb5867da1ad9c777d2fbbe47e4dbdd7'/>
<id>urn:sha1:a60108f7dfb5867da1ad9c777d2fbbe47e4dbdd7</id>
<content type='text'>
No functional change.

Reviewed-by: Daeho Jeong &lt;daehojeong@google.com&gt;
Reviewed-by: Chao Yu &lt;chao@kernel.org&gt;
Signed-off-by: Jaegeuk Kim &lt;jaegeuk@kernel.org&gt;
</content>
</entry>
<entry>
<title>f2fs: show more discard status by sysfs</title>
<updated>2023-12-26T21:07:26Z</updated>
<author>
<name>Zhiguo Niu</name>
</author>
<published>2023-12-20T01:59:58Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c3c2d45b9050180974e35ec8672c6e788adc236a'/>
<id>urn:sha1:c3c2d45b9050180974e35ec8672c6e788adc236a</id>
<content type='text'>
The current pending_discard attr just only shows the discard_cmd_cnt
information. More discard status can be shown so that we can check
them through sysfs when needed.

Signed-off-by: Zhiguo Niu &lt;zhiguo.niu@unisoc.com&gt;
Reviewed-by: Chao Yu &lt;chao@kernel.org&gt;
Signed-off-by: Jaegeuk Kim &lt;jaegeuk@kernel.org&gt;
</content>
</entry>
<entry>
<title>f2fs: Constrain the modification range of dir_level in the sysfs</title>
<updated>2023-12-26T21:06:32Z</updated>
<author>
<name>Yongpeng Yang</name>
</author>
<published>2023-12-22T03:29:00Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0145eed6ed3210f98b366e88363553251c41807d'/>
<id>urn:sha1:0145eed6ed3210f98b366e88363553251c41807d</id>
<content type='text'>
The {struct f2fs_sb_info}-&gt;dir_level can be modified through the sysfs
interface, but its value range is not limited. If the value exceeds
MAX_DIR_HASH_DEPTH and the mount options include "noinline_dentry",
the following error will occur:
[root@fedora ~]# mount -o noinline_dentry /dev/sdb  /mnt/sdb/
[root@fedora ~]# echo 128 &gt; /sys/fs/f2fs/sdb/dir_level
[root@fedora ~]# cd /mnt/sdb/
[root@fedora sdb]# mkdir test
[root@fedora sdb]# cd test/
[root@fedora test]# mkdir test
mkdir: cannot create directory 'test': Argument list too long

Signed-off-by: Yongpeng Yang &lt;yangyongpeng1@oppo.com&gt;
Reviewed-by: Chao Yu &lt;chao@kernel.org&gt;
Signed-off-by: Jaegeuk Kim &lt;jaegeuk@kernel.org&gt;
</content>
</entry>
<entry>
<title>f2fs: sysfs: support discard_io_aware</title>
<updated>2023-11-28T18:59:51Z</updated>
<author>
<name>Chao Yu</name>
</author>
<published>2023-11-22T14:47:15Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d346fa09abff46988de9267b67b6900d9913d5a2'/>
<id>urn:sha1:d346fa09abff46988de9267b67b6900d9913d5a2</id>
<content type='text'>
It gives a way to enable/disable IO aware feature for background
discard, so that we can tune background discard more precisely
based on undiscard condition. e.g. force to disable IO aware if
there are large number of discard extents, and discard IO may
always be interrupted by frequent common IO.

Signed-off-by: Chao Yu &lt;chao@kernel.org&gt;
Signed-off-by: Jaegeuk Kim &lt;jaegeuk@kernel.org&gt;
</content>
</entry>
</feed>
