messages from 2017-02-28 23:41:18 to 2017-03-07 07:34:17 UTC [more...]
[PATCH] zram: set physical queue limits to avoid array out of bounds accesses
2017-03-07 7:23 UTC (9+ messages)
[PATCH 0/11 v3] block: Fix block device shutdown related races
2017-03-07 6:47 UTC (17+ messages)
` [PATCH 01/11] block: Fix bdi assignment to bdev inode when racing with disk delete
` [PATCH 02/11] block: Fix race of bdev open with gendisk shutdown
` [PATCH 03/11] bdi: Mark congested->bdi as internal
` [PATCH 04/11] bdi: Make wb->bdi a proper reference
` [PATCH 05/11] bdi: Move removal from bdi->wb_list into wb_shutdown()
` [PATCH 06/11] bdi: Shutdown writeback on all cgwbs in cgwb_bdi_destroy()
` [PATCH 07/11] bdi: Do not wait for cgwbs release in bdi_unregister()
` [PATCH 08/11] bdi: Rename cgwb_bdi_destroy() to cgwb_bdi_unregister()
` [PATCH 09/11] block: Fix oops in locked_inode_to_wb_and_lock_list()
` [PATCH 10/11] kobject: Export kobject_get_unless_zero()
` [PATCH 11/11] block: Fix oops scsi_disk_get()
cfq-iosched: two questions about the hrtimer version of CFQ
2017-03-07 1:22 UTC (2+ messages)
[PATCH RFC 00/14] Add the BFQ I/O Scheduler to blk-mq
2017-03-07 1:00 UTC (24+ messages)
` [PATCH RFC 01/14] block, bfq: introduce the BFQ-v0 I/O scheduler as an extra scheduler
` [PATCH RFC 02/14] block, bfq: add full hierarchical scheduling and cgroups support
` [PATCH RFC 03/14] block, bfq: improve throughput boosting
` [PATCH RFC 04/14] block, bfq: modify the peak-rate estimator
` [PATCH RFC 05/14] block, bfq: add more fairness with writes and slow processes
` [PATCH RFC 06/14] block, bfq: improve responsiveness
` [PATCH RFC 07/14] block, bfq: reduce I/O latency for soft real-time applications
` [PATCH RFC 08/14] block, bfq: preserve a low latency also with NCQ-capable drives
` [PATCH RFC 09/14] block, bfq: reduce latency during request-pool saturation
` [PATCH RFC 10/14] block, bfq: add Early Queue Merge (EQM)
` [PATCH RFC 11/14] block, bfq: reduce idling only in symmetric scenarios
` [PATCH RFC 12/14] block, bfq: boost the throughput on NCQ-capable flash-based devices
` [PATCH RFC 13/14] block, bfq: boost the throughput with random I/O on NCQ-capable HDDs
` [PATCH RFC 14/14] block, bfq: handle bursts of queue activations
cfq-iosched: two questions about the hrtimer version of CFQ
2017-03-07 0:11 UTC
[PATCH 0/13 v2] block: Fix block device shutdown related races
2017-03-06 20:38 UTC (10+ messages)
[PATCH] block/sed: Fix opal user range check and unused variables
2017-03-06 20:15 UTC (3+ messages)
[PATCH] blkcg: allocate struct blkcg_gq outside request queue spinlock
2017-03-06 20:03 UTC (14+ messages)
` [PATCH v2] "
` [PATCH v3] "
` [PATCH v4] "
[PATCH 0/8 v2] Non-blocking AIO
2017-03-06 18:50 UTC (29+ messages)
` [PATCH 1/8] nowait aio: Introduce IOCB_FLAG_NOWAIT
` [PATCH 2/8] nowait aio: Return if cannot get hold of i_rwsem
` [PATCH 3/8] nowait aio: return if direct write will trigger writeback
` [PATCH 7/8] nowait aio: xfs
[bdi_unregister] 165a5e22fa INFO: task swapper:1 blocked for more than 120 seconds
2017-03-06 17:25 UTC (11+ messages)
` [bdi_unregister] 165a5e22fa BUG kmalloc-512 (Not tainted): Poison overwritten
block/sed-opal.c: 2 * bad if tests ?
2017-03-06 15:19 UTC (2+ messages)
[PATCH] cfq-iosched: fix the delay of cfq_group's vdisktime under iops mode
2017-03-06 13:45 UTC (6+ messages)
WARN_ON() when booting with nvme loopback over zram
2017-03-06 8:35 UTC (3+ messages)
[PATCH v2 00/14] md: cleanup on direct access to bvec table
2017-03-03 17:38 UTC (33+ messages)
` [PATCH v2 04/13] md: prepare for managing resync I/O pages in clean way
` [PATCH v2 05/13] md: raid1: simplify r1buf_pool_free()
` [PATCH v2 06/13] md: raid1: don't use bio's vec table to manage resync pages
` [PATCH v2 08/13] md: raid1: use bio helper in process_checks()
` [PATCH v2 09/13] md: raid1: use bio_segments_all()
` [PATCH v2 11/13] md: raid10: don't use bio's vec table to manage resync pages
` [PATCH v2 13/13] md: raid10: avoid direct access to bvec table in handle_reshape_read_error
[PATCH] block: use put_io_context_active() to disassociate bio from a task
2017-03-03 19:12 UTC (2+ messages)
[PATCH 0/4] blk-mq: cleanup on all kinds of kobjects
2017-03-03 15:34 UTC (2+ messages)
[GIT PULL] Block fixes for 4.11-rc1
2017-03-03 4:07 UTC
[PATCH] blk-mq-sched: don't hold queue_lock when calling exit_icq
2017-03-02 20:59 UTC (14+ messages)
[PATCH] block: Initialize bd_bdi on inode initialization
2017-03-02 15:50 UTC
[WIP BRANCH] cgroups support in bfq-mq WIP branch
2017-03-02 15:19 UTC (4+ messages)
[PATCH 0/3] nvme suspend/resume fix
2017-03-02 7:15 UTC (7+ messages)
` [PATCH 1/3] blk-mq: Export blk_mq_freeze_queue_wait
` [PATCH 2/3] blk-mq: Provide freeze queue timeout
` [PATCH 3/3] nvme: Complete all stuck requests
blk_integrity_revalidate() clears BDI_CAP_STABLE_WRITES
2017-03-02 3:24 UTC (6+ messages)
[PATCH 1/2] loop: fix LO_FLAGS_PARTSCAN hang
2017-03-02 3:07 UTC (6+ messages)
` [PATCH 2/2] blk-mq-debugfs: add q->mq_freeze_depth output
[PATCH 00/16] multiqueue for MMC/SD third try
2017-03-01 17:48 UTC (9+ messages)
` [PATCH 11/16] mmc: block: shuffle retry and error handling
` [PATCH 15/16] mmc: queue: issue requests in massive parallel
[PATCH] nbd: stop leaking sockets
2017-03-01 16:53 UTC (2+ messages)
[PATCH] sbitmap: boundary checks for resized bitmap
2017-03-01 15:39 UTC (3+ messages)
[RFC] failure atomic writes for file systems and block devices
2017-03-01 15:17 UTC (13+ messages)
` [PATCH 05/12] fs: add a F_IOINFO fcntl
` [PATCH 07/12] xfs: implement failure-atomic writes
connect cmd error for nvme-rdma with eventual kernel crash
2017-03-01 15:06 UTC (5+ messages)
[PATCHv2 1/2] blk-mq: Export blk_mq_freeze_queue_wait
2017-03-01 8:54 UTC (9+ messages)
` [PATCHv2 2/2] nvme: Complete all stuck requests
[PATCH 0/3] Separate zone requests from medium access requests
2017-03-01 3:21 UTC (5+ messages)
[PATCH] libsas: add sas_unregister_devs_sas_addr in flutter case
2017-03-01 1:23 UTC
page: next (older) | prev (newer) | latest
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).