diff options
author | Kent Overstreet <kent.overstreet@gmail.com> | 2017-03-19 15:56:34 -0800 |
---|---|---|
committer | Kent Overstreet <kent.overstreet@gmail.com> | 2017-03-19 17:31:47 -0800 |
commit | 5ec39af8eaba49aee7bafa44c661da39e2f40dc3 (patch) | |
tree | 1fb1a981602cbf22c7d2b2dba1168c715d7cecb5 /libbcachefs/movinggc.h | |
parent | bb1941de5378a7b8122d3575dcbc7d0aeb6326f0 (diff) |
Rename from bcache-tools to bcachefs-tools
Diffstat (limited to 'libbcachefs/movinggc.h')
-rw-r--r-- | libbcachefs/movinggc.h | 30 |
1 files changed, 30 insertions, 0 deletions
diff --git a/libbcachefs/movinggc.h b/libbcachefs/movinggc.h new file mode 100644 index 00000000..e27ccc35 --- /dev/null +++ b/libbcachefs/movinggc.h @@ -0,0 +1,30 @@ +#ifndef _BCACHE_MOVINGGC_H +#define _BCACHE_MOVINGGC_H + +/* + * We can't use the entire copygc reserve in one iteration of copygc: we may + * need the buckets we're freeing up to go back into the copygc reserve to make + * forward progress, but if the copygc reserve is full they'll be available for + * any allocation - and it's possible that in a given iteration, we free up most + * of the buckets we're going to free before we allocate most of the buckets + * we're going to allocate. + * + * If we only use half of the reserve per iteration, then in steady state we'll + * always have room in the reserve for the buckets we're going to need in the + * next iteration: + */ +#define COPYGC_BUCKETS_PER_ITER(ca) \ + ((ca)->free[RESERVE_MOVINGGC].size / 2) + +/* + * Max sectors to move per iteration: Have to take into account internal + * fragmentation from the multiple write points for each generation: + */ +#define COPYGC_SECTORS_PER_ITER(ca) \ + ((ca)->mi.bucket_size * COPYGC_BUCKETS_PER_ITER(ca)) + +void bch2_moving_gc_stop(struct bch_dev *); +int bch2_moving_gc_start(struct bch_dev *); +void bch2_dev_moving_gc_init(struct bch_dev *); + +#endif |