forked from torvalds/linux
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge tag 'for-5.3/block-20190708' of git://git.kernel.dk/linux-block
Pull block updates from Jens Axboe:
"This is the main block updates for 5.3. Nothing earth shattering or
major in here, just fixes, additions, and improvements all over the
map. This contains:
- Series of documentation fixes (Bart)
- Optimization of the blk-mq ctx get/put (Bart)
- null_blk removal race condition fix (Bob)
- req/bio_op() cleanups (Chaitanya)
- Series cleaning up the segment accounting, and request/bio mapping
(Christoph)
- Series cleaning up the page getting/putting for bios (Christoph)
- block cgroup cleanups and moving it to where it is used (Christoph)
- block cgroup fixes (Tejun)
- Series of fixes and improvements to bcache, most notably a write
deadlock fix (Coly)
- blk-iolatency STS_AGAIN and accounting fixes (Dennis)
- Series of improvements and fixes to BFQ (Douglas, Paolo)
- debugfs_create() return value check removal for drbd (Greg)
- Use struct_size(), where appropriate (Gustavo)
- Two lighnvm fixes (Heiner, Geert)
- MD fixes, including a read balance and corruption fix (Guoqing,
Marcos, Xiao, Yufen)
- block opal shadow mbr additions (Jonas, Revanth)
- sbitmap compare-and-exhange improvemnts (Pavel)
- Fix for potential bio->bi_size overflow (Ming)
- NVMe pull requests:
- improved PCIe suspent support (Keith Busch)
- error injection support for the admin queue (Akinobu Mita)
- Fibre Channel discovery improvements (James Smart)
- tracing improvements including nvmetc tracing support (Minwoo Im)
- misc fixes and cleanups (Anton Eidelman, Minwoo Im, Chaitanya
Kulkarni)"
- Various little fixes and improvements to drivers and core"
* tag 'for-5.3/block-20190708' of git://git.kernel.dk/linux-block: (153 commits)
blk-iolatency: fix STS_AGAIN handling
block: nr_phys_segments needs to be zero for REQ_OP_WRITE_ZEROES
blk-mq: simplify blk_mq_make_request()
blk-mq: remove blk_mq_put_ctx()
sbitmap: Replace cmpxchg with xchg
block: fix .bi_size overflow
block: sed-opal: check size of shadow mbr
block: sed-opal: ioctl for writing to shadow mbr
block: sed-opal: add ioctl for done-mark of shadow mbr
block: never take page references for ITER_BVEC
direct-io: use bio_release_pages in dio_bio_complete
block_dev: use bio_release_pages in bio_unmap_user
block_dev: use bio_release_pages in blkdev_bio_end_io
iomap: use bio_release_pages in iomap_dio_bio_end_io
block: use bio_release_pages in bio_map_user_iov
block: use bio_release_pages in bio_unmap_user
block: optionally mark pages dirty in bio_release_pages
block: move the BIO_NO_PAGE_REF check into bio_release_pages
block: skd_main.c: Remove call to memset after dma_alloc_coherent
block: mtip32xx: Remove call to memset after dma_alloc_coherent
...- Loading branch information
Showing
104 changed files
with
3,368 additions
and
1,554 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -14,6 +14,15 @@ add_random (RW) | |
| This file allows to turn off the disk entropy contribution. Default | ||
| value of this file is '1'(on). | ||
|
|
||
| chunk_sectors (RO) | ||
| ------------------ | ||
| This has different meaning depending on the type of the block device. | ||
| For a RAID device (dm-raid), chunk_sectors indicates the size in 512B sectors | ||
| of the RAID volume stripe segment. For a zoned block device, either host-aware | ||
| or host-managed, chunk_sectors indicates the size in 512B sectors of the zones | ||
| of the device, with the eventual exception of the last zone of the device which | ||
| may be smaller. | ||
|
|
||
| dax (RO) | ||
| -------- | ||
| This file indicates whether the device supports Direct Access (DAX), | ||
|
|
@@ -43,6 +52,16 @@ large discards are issued, setting this value lower will make Linux issue | |
| smaller discards and potentially help reduce latencies induced by large | ||
| discard operations. | ||
|
|
||
| discard_zeroes_data (RO) | ||
| ------------------------ | ||
| Obsolete. Always zero. | ||
|
|
||
| fua (RO) | ||
| -------- | ||
| Whether or not the block driver supports the FUA flag for write requests. | ||
| FUA stands for Force Unit Access. If the FUA flag is set that means that | ||
| write requests must bypass the volatile cache of the storage device. | ||
|
|
||
| hw_sector_size (RO) | ||
| ------------------- | ||
| This is the hardware sector size of the device, in bytes. | ||
|
|
@@ -83,14 +102,19 @@ logical_block_size (RO) | |
| ----------------------- | ||
| This is the logical block size of the device, in bytes. | ||
|
|
||
| max_discard_segments (RO) | ||
| ------------------------- | ||
| The maximum number of DMA scatter/gather entries in a discard request. | ||
|
|
||
| max_hw_sectors_kb (RO) | ||
| ---------------------- | ||
| This is the maximum number of kilobytes supported in a single data transfer. | ||
|
|
||
| max_integrity_segments (RO) | ||
| --------------------------- | ||
| When read, this file shows the max limit of integrity segments as | ||
| set by block layer which a hardware controller can handle. | ||
| Maximum number of elements in a DMA scatter/gather list with integrity | ||
| data that will be submitted by the block layer core to the associated | ||
| block driver. | ||
|
|
||
| max_sectors_kb (RW) | ||
| ------------------- | ||
|
|
@@ -100,11 +124,12 @@ size allowed by the hardware. | |
|
|
||
| max_segments (RO) | ||
| ----------------- | ||
| Maximum number of segments of the device. | ||
| Maximum number of elements in a DMA scatter/gather list that is submitted | ||
| to the associated block driver. | ||
|
|
||
| max_segment_size (RO) | ||
| --------------------- | ||
| Maximum segment size of the device. | ||
| Maximum size in bytes of a single element in a DMA scatter/gather list. | ||
|
|
||
| minimum_io_size (RO) | ||
| -------------------- | ||
|
|
@@ -132,6 +157,12 @@ per-block-cgroup request pool. IOW, if there are N block cgroups, | |
| each request queue may have up to N request pools, each independently | ||
| regulated by nr_requests. | ||
|
|
||
| nr_zones (RO) | ||
| ------------- | ||
| For zoned block devices (zoned attribute indicating "host-managed" or | ||
| "host-aware"), this indicates the total number of zones of the device. | ||
| This is always 0 for regular block devices. | ||
|
|
||
| optimal_io_size (RO) | ||
| -------------------- | ||
| This is the optimal IO size reported by the device. | ||
|
|
@@ -185,8 +216,8 @@ This is the number of bytes the device can write in a single write-same | |
| command. A value of '0' means write-same is not supported by this | ||
| device. | ||
|
|
||
| wb_lat_usec (RW) | ||
| ---------------- | ||
| wbt_lat_usec (RW) | ||
| ----------------- | ||
| If the device is registered for writeback throttling, then this file shows | ||
| the target minimum read latency. If this latency is exceeded in a given | ||
| window of time (see wb_window_usec), then the writeback throttling will start | ||
|
|
@@ -201,6 +232,12 @@ blk-throttle makes decision based on the samplings. Lower time means cgroups | |
| have more smooth throughput, but higher CPU overhead. This exists only when | ||
| CONFIG_BLK_DEV_THROTTLING_LOW is enabled. | ||
|
|
||
| write_zeroes_max_bytes (RO) | ||
| --------------------------- | ||
| For block drivers that support REQ_OP_WRITE_ZEROES, the maximum number of | ||
| bytes that can be zeroed at once. The value 0 means that REQ_OP_WRITE_ZEROES | ||
| is not supported. | ||
|
|
||
| zoned (RO) | ||
| ---------- | ||
| This indicates if the device is a zoned block device and the zone model of the | ||
|
|
@@ -213,19 +250,4 @@ devices are described in the ZBC (Zoned Block Commands) and ZAC | |
| do not support zone commands, they will be treated as regular block devices | ||
| and zoned will report "none". | ||
|
|
||
| nr_zones (RO) | ||
| ------------- | ||
| For zoned block devices (zoned attribute indicating "host-managed" or | ||
| "host-aware"), this indicates the total number of zones of the device. | ||
| This is always 0 for regular block devices. | ||
|
|
||
| chunk_sectors (RO) | ||
| ------------------ | ||
| This has different meaning depending on the type of the block device. | ||
| For a RAID device (dm-raid), chunk_sectors indicates the size in 512B sectors | ||
| of the RAID volume stripe segment. For a zoned block device, either host-aware | ||
| or host-managed, chunk_sectors indicates the size in 512B sectors of the zones | ||
| of the device, with the eventual exception of the last zone of the device which | ||
| may be smaller. | ||
|
|
||
| Jens Axboe <[email protected]>, February 2009 | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.