kernel.git/drivers/md/dm-stats.c, branch linux-4.9.y

dm stats: add cond_resched when looping over entries

2022-06-06T06:19:46Z

commit bfe2b0146c4d0230b68f5c71a64380ff8d361f8b upstream. dm-stats can be used with a very large number of entries (it is only limited by 1/4 of total system memory), so add rescheduling points to the loops that iterate over the entries. Cc: stable@vger.kernel.org Signed-off-by: Mikulas Patocka Signed-off-by: Mike Snitzer Signed-off-by: Greg Kroah-Hartman

dm stats: fix a leaked s->histogram_boundaries array

2017-03-12T05:41:44Z

commit 6085831883c25860264721df15f05bbded45e2a2 upstream. Fixes: dfcfac3e4cd9 ("dm stats: collect and report histogram of IO latencies") Signed-off-by: Mikulas Patocka Signed-off-by: Mike Snitzer Signed-off-by: Greg Kroah-Hartman

dm: move request-based code out to dm-rq.[hc]

2016-06-10T19:15:44Z

Add some seperation between bio-based and request-based DM core code. 'struct mapped_device' and other DM core only structures and functions have been moved to dm-core.h and all relevant DM core .c files have been updated to include dm-core.h rather than dm.h DM targets should _never_ include dm-core.h! [block core merge conflict resolution from Stephen Rothwell] Signed-off-by: Mike Snitzer Signed-off-by: Stephen Rothwell

dm: pass dm stats data dir instead of bi_rw

2016-06-07T19:41:38Z

It looks like dm stats cares about the data direction (READ vs WRITE) and does not need the bio/request flags. Commands like REQ_FLUSH, REQ_DISCARD and REQ_WRITE_SAME are currently always set with REQ_WRITE, so the extra check for REQ_DISCARD in dm_stats_account_io is not needed. This patch has it use the bio and request data_dir helpers instead of accessing the bi_rw/cmd_flags directly. This makes the next patches that remove the operation from the cmd_flags and bi_rw easier, because we will no longer have the REQ_WRITE bit set for operations like discards. Signed-off-by: Mike Christie Reviewed-by: Christoph Hellwig Reviewed-by: Hannes Reinecke Signed-off-by: Jens Axboe

dm stats: report precise_timestamps and histogram in @stats_list output

2015-08-18T21:20:03Z

If the user selected the precise_timestamps or histogram options, report it in the @stats_list message output. If the user didn't select these options, no extra tokens are reported, thus it is backward compatible with old software that doesn't know about precise timestamps and histogram. Signed-off-by: Mikulas Patocka Signed-off-by: Mike Snitzer Cc: stable@vger.kernel.org # 4.2

dm stats: add support for request-based DM devices

2015-06-17T16:40:41Z

This makes it possible to use dm stats with DM multipath. Signed-off-by: Mikulas Patocka Signed-off-by: Mike Snitzer

dm stats: collect and report histogram of IO latencies

2015-06-17T16:40:40Z

Add an option to dm statistics to collect and report a histogram of IO latencies. Signed-off-by: Mikulas Patocka Signed-off-by: Mike Snitzer

dm stats: support precise timestamps

2015-06-17T16:40:40Z

Make it possible to use precise timestamps with nanosecond granularity in dm statistics. Signed-off-by: Mikulas Patocka Signed-off-by: Mike Snitzer

dm stats: fix divide by zero if 'number_of_areas' arg is zero

2015-06-17T16:40:39Z

If the number_of_areas argument was zero the kernel would crash on div-by-zero. Add better input validation. Signed-off-by: Mikulas Patocka Signed-off-by: Mike Snitzer Cc: stable@vger.kernel.org # v3.12+

dm stats: Use kvfree() in dm_kvfree()

2015-06-11T21:13:02Z

Use kvfree() instead of open-coding it. Signed-off-by: Pekka Enberg Signed-off-by: Mike Snitzer