summaryrefslogtreecommitdiff
path: root/fs/bcachefs/io_write.c
diff options
context:
space:
mode:
authorKent Overstreet <kent.overstreet@linux.dev>2025-01-30 03:41:31 -0500
committerKent Overstreet <kent.overstreet@linux.dev>2025-03-14 21:02:10 -0400
commit55a132c37acded02391664c108fcea5006c72fd5 (patch)
treeb03b9cfcc4c12eb71a7e18f3cedc0bcb57b5b0fb /fs/bcachefs/io_write.c
parente5a63ad343cc19c64875f2496ce5f7b992ef0c32 (diff)
bcachefs: Don't inc io_(read|write) counters for moves
This makes 'bcachefs fs top' more useful; we can now see at a glance whether the IO to the device is being done for user reads/writes, or copygc/rebalance. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
Diffstat (limited to 'fs/bcachefs/io_write.c')
-rw-r--r--fs/bcachefs/io_write.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/fs/bcachefs/io_write.c b/fs/bcachefs/io_write.c
index 03892388832b..970f3f0959a4 100644
--- a/fs/bcachefs/io_write.c
+++ b/fs/bcachefs/io_write.c
@@ -1644,7 +1644,8 @@ CLOSURE_CALLBACK(bch2_write)
goto err;
}
- this_cpu_add(c->counters[BCH_COUNTER_io_write], bio_sectors(bio));
+ if (!(op->flags & BCH_WRITE_MOVE))
+ this_cpu_add(c->counters[BCH_COUNTER_io_write], bio_sectors(bio));
bch2_increment_clock(c, bio_sectors(bio), WRITE);
data_len = min_t(u64, bio->bi_iter.bi_size,