2005-11-04 10:43:35 +03:00
#
# Makefile for the kernel block layer
#
2014-05-19 18:16:41 +04:00
obj-$(CONFIG_BLOCK) := bio.o elevator.o blk-core.o blk-tag.o blk-sysfs.o \
2010-09-03 13:56:16 +04:00
blk-flush.o blk-settings.o blk-ioc.o blk-map.o \
2008-09-14 16:55:09 +04:00
blk-exec.o blk-merge.o blk-softirq.o blk-timeout.o \
2016-11-08 07:32:37 +03:00
blk-lib.o blk-mq.o blk-mq-tag.o blk-stat.o \
2017-01-17 16:03:22 +03:00
blk-mq-sysfs.o blk-mq-cpumap.o blk-mq-sched.o ioctl.o \
2017-01-28 11:32:51 +03:00
genhd.o partition-generic.o ioprio.o \
2015-12-25 05:20:32 +03:00
badblocks.o partitions/
2005-11-04 10:43:35 +03:00
2017-01-28 11:32:51 +03:00
obj-$(CONFIG_BOUNCE) += bounce.o
obj-$(CONFIG_BLK_SCSI_REQUEST) += scsi_ioctl.o
2007-07-09 14:38:05 +04:00
obj-$(CONFIG_BLK_DEV_BSG) += bsg.o
2011-08-01 00:05:09 +04:00
obj-$(CONFIG_BLK_DEV_BSGLIB) += bsg-lib.o
2009-12-03 20:59:42 +03:00
obj-$(CONFIG_BLK_CGROUP) += blk-cgroup.o
2010-09-16 01:06:35 +04:00
obj-$(CONFIG_BLK_DEV_THROTTLING) += blk-throttle.o
2005-11-04 10:43:35 +03: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 03:11:11 +03:00
obj-$(CONFIG_MQ_IOSCHED_DEADLINE) += mq-deadline.o
2017-04-14 11:00:02 +03:00
obj-$(CONFIG_MQ_IOSCHED_KYBER) += kyber-iosched.o
2017-04-19 17:48:24 +03:00
bfq-y := bfq-iosched.o bfq-wf2q.o bfq-cgroup.o
obj-$(CONFIG_IOSCHED_BFQ) += bfq.o
2006-03-23 22:00:26 +03:00
2007-10-12 14:50:41 +04:00
obj-$(CONFIG_BLOCK_COMPAT) += compat_ioctl.o
2013-10-01 00:45:19 +04:00
obj-$(CONFIG_BLK_CMDLINE_PARSER) += cmdline-parser.o
2014-09-27 03:20:07 +04:00
obj-$(CONFIG_BLK_DEV_INTEGRITY) += bio-integrity.o blk-integrity.o t10-pi.o
2016-09-19 08:50:16 +03:00
obj-$(CONFIG_BLK_MQ_PCI) += blk-mq-pci.o
2017-02-05 20:15:24 +03:00
obj-$(CONFIG_BLK_MQ_VIRTIO) += blk-mq-virtio.o
2016-10-18 09:40:33 +03: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 22:36:15 +03:00
obj-$(CONFIG_BLK_WBT) += blk-wbt.o
2017-01-28 01:03:01 +03:00
obj-$(CONFIG_BLK_DEBUG_FS) += blk-mq-debugfs.o
2017-02-03 22:50:31 +03:00
obj-$(CONFIG_BLK_SED_OPAL) += sed-opal.o