linux.git/fs/f2fs/sysfs.c, branch v4.15

f2fs: add quota_ino feature infra

2017-11-06T00:42:01+00:00

This patch adds quota_ino feature infra to be used for quota files.

Reviewed-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: export SSR allocation threshold

2017-11-06T00:41:57+00:00

This patch exports min_ssr_segments threshold in sysfs to let user
control triggering SSR allocation flexibly.

Signed-off-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: support soft block reservation

2017-11-06T00:41:52+00:00

It supports to extend reserved_blocks sysfs interface to be soft
threshold, which allows user configure it exceeding current available
user space. This patch also introduces a new sysfs interface called
current_reserved_blocks, which shows the current blocks that have
already been reserved.

Signed-off-by: Yunlong Song 
Signed-off-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: support flexible inline xattr size

2017-11-06T00:41:50+00:00

Now, in product, more and more features based on file encryption were
introduced, their demand of xattr space is increasing, however, inline
xattr has fixed-size of 200 bytes, once inline xattr space is full, new
increased xattr data would occupy additional xattr block which may bring
us more space usage and performance regression during persisting.

In order to resolve above issue, it's better to expand inline xattr size
flexibly according to user's requirement.

So this patch introduces new filesystem feature 'flexible inline xattr',
and new mount option 'inline_xattr_size=%u', once mkfs enables the
feature, we can use the option to make f2fs supporting flexible inline
xattr size.

To support this feature, we add extra attribute i_inline_xattr_size in
inode layout, indicating that how many space inline xattr borrows from
block address mapping space in inode layout, by this, we can easily
locate and store flexible-sized inline xattr data in inode.

Inode disk layout:
  +----------------------+
  | .i_mode              |
  | ...                  |
  | .i_ext               |
  +----------------------+
  | .i_extra_isize       |
  | .i_inline_xattr_size |-----------+
  | ...                  |           |
  +----------------------+           |
  | .i_addr              |           |
  |  - block address or  |           |
  |  - inline data       |           |
  +----------------------+<---+      v
  |    inline xattr      |    +---inline xattr range
  +----------------------+<---+
  | .i_nid               |
  +----------------------+
  |   node_footer        |
  | (nid, ino, offset)   |
  +----------------------+

Note that, we have to cnosider backward compatibility which reserved
inline_data space, 200 bytes, all the time, reported by Sheng Yong.

Previous inline data or directory always reserved 200 bytes in inode layout,
even if inline_xattr is disabled. In order to keep inline_dentry's structure
for backward compatibility, we get the space back only from inline_data.

Signed-off-by: Chao Yu 
Reported-by: Sheng Yong 
Signed-off-by: Jaegeuk Kim

f2fs: show # of dirty segments via sysfs

2017-11-06T00:41:47+00:00

This patch adds one sysfs entry to show # of dirty segments which can be
used for gc timing by user.

Reviewed-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: split discard policy

2017-10-26T08:44:08+00:00

There are many different scenarios such as fstrim, umount, urgent or
background where we will issue discards, actually, they need use
different policy in aspect of io aware, discard granularity, delay
interval and so on. But now they just share one common discard policy,
so there will be race when changing policy in between these scenarios,
the interference of changing discard policy will be very serious.

This patch changes to split discard policy for different scenarios.

Signed-off-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: fix to show correct discard_granularity in sysfs

2017-09-12T17:02:47+00:00

Fix below incorrect display when reading discard_granularity sysfs node.

$ cat /sys/fs/f2fs//discard_granularity
$ 16
$ echo 32 > /sys/fs/f2fs//discard_granularity
$ cat /sys/fs/f2fs//discard_granularity
$ 16

Signed-off-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: wake up discard_thread iff there is a candidate

2017-08-29T17:05:33+00:00

This patch fixes to avoid needless wake ups.

Reviewed-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: issue discard commands if gc_urgent is set

2017-08-29T17:02:47+00:00

It's time to issue all the discard commands, if user sets the idle time.

Reviewed-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: introduce discard_granularity sysfs entry

2017-08-21T22:55:07+00:00

Commit d618ebaf0aa8 ("f2fs: enable small discard by default") enables
f2fs to issue 4K size discard in real-time discard mode. However, issuing
smaller discard may cost more lifetime but releasing less free space in
flash device. Since f2fs has ability of separating hot/cold data and
garbage collection, we can expect that small-sized invalid region would
expand soon with OPU, deletion or garbage collection on valid datas, so
it's better to delay or skip issuing smaller size discards, it could help
to reduce overmuch consumption of IO bandwidth and lifetime of flash
storage.

This patch makes f2fs selectng 64K size as its default minimal
granularity, and issue discard with the size which is not smaller than
minimal granularity. Also it exposes discard granularity as sysfs entry
for configuration in different scenario.

Jaegeuk Kim:
 We must issue all the accumulated discard commands when fstrim is called.
 So, I've added pend_list_tag[] to indicate whether we should issue the
 commands or not. If tag sets P_ACTIVE or P_TRIM, we have to issue them.
 P_TRIM is set once at a time, given fstrim trigger.
 In addition, issue_discard_thread is calling too much due to the number of
 discard commands remaining in the pending list. I added a timer to control
 it likewise gc_thread.

Signed-off-by: Chao Yu 
Signed-off-by: Jaegeuk Kim