Hi Andreas, I like the idea you're introducing; should lessen trashing by GC on my workstations. On Tuesday 21 of January 2014 14:59:40 you wrote: > With this option the user can specify the minimal number of free/dead > blocks before a segment can be cleaned. This is a threshold for the GC > to prevent needless moving of data. If there are less free blocks > to gain from cleaning a segment than the specified number, the GC will > abort and try again with a different segment. Will your patches be smart enough to re-claim space if the only available free blocks are under threshold? Scenario: FS is running out of free space, and the free blocks to be reclaimed are scattered through segments in small numbers. Several segments have a small number of free blocks, but in each segment the amount is under the threshold. Regards, -- dexen deVries [[[↓][→]]] -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
