btrfs: balance filter: add limit of processed chunks
This started as debugging helper, to watch the effects of converting between raid levels on multiple devices, but could be useful standalone. In my case the usage filter was not finegrained enough and led to converting too many chunks at once. Another example use is in connection with drange+devid or vrange filters that allow to work with a specific chunk or even with a chunk on a given device. The limit filter applies last, the value of 0 means no limiting. CC: Ilya Dryomov <idryomov@gmail.com> CC: Hugo Mills <hugo@carfax.org.uk> Signed-off-by: David Sterba <dsterba@suse.cz> Signed-off-by: Chris Mason <clm@fb.com>
This commit is contained in:

committed by
Chris Mason

parent
fc19c5e736
commit
7d824b6f9c
@@ -840,7 +840,10 @@ struct btrfs_disk_balance_args {
|
||||
/* BTRFS_BALANCE_ARGS_* */
|
||||
__le64 flags;
|
||||
|
||||
__le64 unused[8];
|
||||
/* BTRFS_BALANCE_ARGS_LIMIT value */
|
||||
__le64 limit;
|
||||
|
||||
__le64 unused[7];
|
||||
} __attribute__ ((__packed__));
|
||||
|
||||
/*
|
||||
@@ -2897,6 +2900,7 @@ btrfs_disk_balance_args_to_cpu(struct btrfs_balance_args *cpu,
|
||||
cpu->vend = le64_to_cpu(disk->vend);
|
||||
cpu->target = le64_to_cpu(disk->target);
|
||||
cpu->flags = le64_to_cpu(disk->flags);
|
||||
cpu->limit = le64_to_cpu(disk->limit);
|
||||
}
|
||||
|
||||
static inline void
|
||||
@@ -2914,6 +2918,7 @@ btrfs_cpu_balance_args_to_disk(struct btrfs_disk_balance_args *disk,
|
||||
disk->vend = cpu_to_le64(cpu->vend);
|
||||
disk->target = cpu_to_le64(cpu->target);
|
||||
disk->flags = cpu_to_le64(cpu->flags);
|
||||
disk->limit = cpu_to_le64(cpu->limit);
|
||||
}
|
||||
|
||||
/* struct btrfs_super_block */
|
||||
|
Reference in New Issue
Block a user