summaryrefslogtreecommitdiff
path: root/fs/bcachefs/ec.c
diff options
context:
space:
mode:
authorKent Overstreet <kent.overstreet@linux.dev>2023-03-01 21:47:07 -0500
committerKent Overstreet <kent.overstreet@linux.dev>2023-10-22 17:09:55 -0400
commit910659763edaba58aa04bd5924dd933bc08cc56f (patch)
tree572a22a75d5a45db070052e7830b13088426e00d /fs/bcachefs/ec.c
parent3329cf1bb91d6293a96cf35ad72b2a2e1e1c0e3d (diff)
downloadlwn-910659763edaba58aa04bd5924dd933bc08cc56f.tar.gz
lwn-910659763edaba58aa04bd5924dd933bc08cc56f.zip
bcachefs: Mark stripe buckets with correct data type
Currently, we don't use bucket data type for tracking whether buckets are part of a stripe; parity buckets are BCH_DATA_parity, but data buckets in a stripe are BCH_DATA_user. There's a separate counter, buckets_ec, outside the BCH_DATA_TYPES system for tracking number of buckets on a device that are part of a stripe. The trouble with this approach is that it's too coarse grained, and we need better information on fragmentation for debugging copygc. With this patch, data buckets in a stripe are now tracked as BCH_DATA_stripe buckets. This doesn't yet differentiate between erasure coded and non-erasure coded data in a stripe bucket, nor do we yet track empty data buckets in stripes. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
Diffstat (limited to 'fs/bcachefs/ec.c')
0 files changed, 0 insertions, 0 deletions