Chao, > Not sure, we will add gc_urgent_low_remaining later...
> Can we share the same interface for all gc_mode? since each mode is exclusive. > Thoughts? Both GC urgent mid mode and GC urgent high mode run using the urgent_sleep_time interval. If the user program does not switch back to normal mode in an abnormal state, it will cause the gc to run rapidly. Therefore, there needs to be a mechanism to ensure that the GC urgent mid mode and GC urgent high mode can be switched back to the normal mode. Since there is currently a gc_urgent_high_remaining node, I added the gc_urgent_mid_remaining node. If gc_urgent_high_remaining can act on three modes, it is not in line with the meaning of the name. Not sure if the existing sys node can still change the name, if it can be changed, obviously using gc_urgent_remaining is a better way. Can an existing node still be renamed? If the name cannot be changed, it is necessary to increase gc_urgent_mid_remaining. Perhaps one more gc_urgent_low_remaining could be added? _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
