2005-11-04 07:43:35 +00:00
|
|
|
#
|
|
|
|
# Makefile for the kernel block layer
|
|
|
|
#
|
|
|
|
|
2014-05-19 14:16:41 +00:00
|
|
|
obj-$(CONFIG_BLOCK) := bio.o elevator.o blk-core.o blk-tag.o blk-sysfs.o \
|
2010-09-03 09:56:16 +00:00
|
|
|
blk-flush.o blk-settings.o blk-ioc.o blk-map.o \
|
2008-09-14 12:55:09 +00:00
|
|
|
blk-exec.o blk-merge.o blk-softirq.o blk-timeout.o \
|
2016-11-08 04:32:37 +00:00
|
|
|
blk-lib.o blk-mq.o blk-mq-tag.o blk-stat.o \
|
2017-01-17 13:03:22 +00:00
|
|
|
blk-mq-sysfs.o blk-mq-cpumap.o blk-mq-sched.o ioctl.o \
|
2014-05-19 17:02:18 +00:00
|
|
|
genhd.o scsi_ioctl.o partition-generic.o ioprio.o \
|
2015-12-25 02:20:32 +00:00
|
|
|
badblocks.o partitions/
|
2005-11-04 07:43:35 +00:00
|
|
|
|
2014-05-20 02:01:52 +00:00
|
|
|
obj-$(CONFIG_BOUNCE) += bounce.o
|
2007-07-09 10:38:05 +00:00
|
|
|
obj-$(CONFIG_BLK_DEV_BSG) += bsg.o
|
2011-07-31 20:05:09 +00:00
|
|
|
obj-$(CONFIG_BLK_DEV_BSGLIB) += bsg-lib.o
|
2009-12-03 17:59:42 +00:00
|
|
|
obj-$(CONFIG_BLK_CGROUP) += blk-cgroup.o
|
2010-09-15 21:06:35 +00:00
|
|
|
obj-$(CONFIG_BLK_DEV_THROTTLING) += blk-throttle.o
|
2005-11-04 07:43:35 +00:00
|
|
|
obj-$(CONFIG_IOSCHED_NOOP) += noop-iosched.o
|
|
|
|
obj-$(CONFIG_IOSCHED_DEADLINE) += deadline-iosched.o
|
|
|
|
obj-$(CONFIG_IOSCHED_CFQ) += cfq-iosched.o
|
2017-01-15 00:11:11 +00:00
|
|
|
obj-$(CONFIG_MQ_IOSCHED_DEADLINE) += mq-deadline.o
|
2006-03-23 19:00:26 +00:00
|
|
|
|
2007-10-12 10:50:41 +00:00
|
|
|
obj-$(CONFIG_BLOCK_COMPAT) += compat_ioctl.o
|
2013-09-30 20:45:19 +00:00
|
|
|
obj-$(CONFIG_BLK_CMDLINE_PARSER) += cmdline-parser.o
|
2014-09-26 23:20:07 +00:00
|
|
|
obj-$(CONFIG_BLK_DEV_INTEGRITY) += bio-integrity.o blk-integrity.o t10-pi.o
|
2016-09-19 05:50:16 +00:00
|
|
|
obj-$(CONFIG_BLK_MQ_PCI) += blk-mq-pci.o
|
2016-10-18 06:40:33 +00:00
|
|
|
obj-$(CONFIG_BLK_DEV_ZONED) += blk-zoned.o
|
blk-wbt: add general throttling mechanism
We can hook this up to the block layer, to help throttle buffered
writes.
wbt registers a few trace points that can be used to track what is
happening in the system:
wbt_lat: 259:0: latency 2446318
wbt_stat: 259:0: rmean=2446318, rmin=2446318, rmax=2446318, rsamples=1,
wmean=518866, wmin=15522, wmax=5330353, wsamples=57
wbt_step: 259:0: step down: step=1, window=72727272, background=8, normal=16, max=32
This shows a sync issue event (wbt_lat) that exceeded it's time. wbt_stat
dumps the current read/write stats for that window, and wbt_step shows a
step down event where we now scale back writes. Each trace includes the
device, 259:0 in this case.
Signed-off-by: Jens Axboe <axboe@fb.com>
2016-11-09 19:36:15 +00:00
|
|
|
obj-$(CONFIG_BLK_WBT) += blk-wbt.o
|
2017-01-25 16:06:40 +00:00
|
|
|
obj-$(CONFIG_DEBUG_FS) += blk-mq-debugfs.o
|