[PATCH] lightnvm: pblk: fix bad free seq. on error path

Braces around the error patch for metadata pre-allocation are wrongly placed. This causes a memory leak in case of a memory allocation failure. Fix it Signed-off-by: Javier González --- drivers/lightnvm/pblk-init.c | 30 +++--- 1 file changed, 15

[GIT PULL] libnvdimm fixes for 4.12-rc1

Hi Linus, please pull from: git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm libnvdimm-fixes ...to receive some incremental fixes and a small feature addition relative to the libnvdimm 4.12 pull request. * Geert noticed that tinyconfig was bloated by BLOCK selecting DAX. The size

RE: [PATCH 5/5] mmc: block: move multi-ioctl() to use block layer

> -Original Message- > From: linux-mmc-ow...@vger.kernel.org [mailto:linux-mmc- > ow...@vger.kernel.org] On Behalf Of Linus Walleij > Sent: Wednesday, May 10, 2017 11:24 AM > To: linux-...@vger.kernel.org; Ulf Hansson ; > Adrian Hunter >

Re: Kyber scheduler brings system to halt when used on swap partition

On Thu, May 11, 2017 at 02:57:24PM +0200, Markus Trippelsdorf wrote: > Using the new Kyber mq scheduler brings my system to a halt as soon as it > starts swapping. The swap partition resides on an SSD and is the only > partition in use on that drive. > Symptoms are stuttering sound and non moving

Announcing blktests

Hi, everyone, At LSF/MM, we talked about the need for somewhere to dump tests for the block layer/storage stack. I've put together a test suite inspired by xfstests here: https://github.com/osandov/blktests. I started out with the opinion that we should reuse xfstests for this, but it became

[PATCH] blk-mq: provide a default .bio_merge

Before blk-mq is introduced, I/O is merged before putting into plug queue, but blk-mq changed the order and makes merging basically impossible until mq-deadline is introduced. Then it is observed that throughput of sequential I/O is degraded about 10%~20% on virtio-blk in the test[1] if IO

APPLY FOR YOUR URGENT LOAN AT 2%

* Do you need an urgent loan? We offer all kinds of loan * Very fast and urgent transfer to your bank account. * Payment begins (6) months after you get the money in your bank account * Low interest rates 2% * Payment of long-term (1-30 years) duration For more information and loan application

[PATCH v4 4/4] blk-mq: allow to use hw tag for shared tags

In case of shared tags, hctx_may_queue() limits that the maximum number of requests allocated to one hw queue is .queue_depth / active_queues. So we try to allow to use hw tag for this case if .queue_depth/shared_queues is not less than q->nr_requests. This can cover some scsi devices too, such

[PATCH v4 3/4] blk-mq: use hw tag for scheduling if hw tag space is big enough

When tag space of one device is big enough, we use hw tag directly for I/O scheduling. Now the decision is made if hw queue depth is not less than q->nr_requests and the tag set isn't shared. Signed-off-by: Ming Lei --- block/blk-mq-sched.c | 71

[PATCH v4 0/4] blk-mq: support to use hw tag for scheduling

Hi, This patchset introduces flag of BLK_MQ_F_SCHED_USE_HW_TAG and allows to use hardware tag directly for IO scheduling if the queue's depth is big enough. In this way, we can avoid to allocate extra tags and request pool for IO schedule, and the schedule tag allocation/release can be saved in

[PATCH v4 1/4] blk-mq: introduce BLK_MQ_F_SCHED_USE_HW_TAG

When blk-mq I/O scheduler is used, we need two tags for submitting one request. One is called scheduler tag for allocating request and scheduling I/O, another one is called driver tag, which is used for dispatching IO to hardware/driver. This way introduces one extra per-queue allocation for both

[PATCH v4 2/4] blk-mq: introduce blk_mq_get_queue_depth()

The hardware queue depth can be resized via blk_mq_update_nr_requests(), so introduce this helper for retrieving queue's depth easily. Reviewed-by: Omar Sandoval Signed-off-by: Ming Lei --- block/blk-mq.c | 15 +++ block/blk-mq.h | 1 + 2 files

[PATCH v4 0/4] blk-mq: support to use hw tag for scheduling

Hi, This patchset introduces flag of BLK_MQ_F_SCHED_USE_HW_TAG and allows to use hardware tag directly for IO scheduling if the queue's depth is big enough. In this way, we can avoid to allocate extra tags and request pool for IO schedule, and the schedule tag allocation/release can be saved in

Re: [RFC PATCH 3/3] mmc: core: Allow mmc block device to re-claim the host

On 11/05/17 15:39, Ulf Hansson wrote: > The current mmc block device implementation is tricky when it comes to > claim and release of the host, while processing I/O requests. In principle > we need to claim the host at the first request entering the queue and then > we need to release the host, as

Re: [RFC PATCH 1/3] mmc: sdio: Don't use abort-able claim host method from SDIO IRQ thread

On 11/05/17 15:39, Ulf Hansson wrote: > In a step to simplify the use of the lock, mmc_claim|release_host(), let's > change the SDIO IRQ thread to move away from using the abort-able claim > host method. > > In the SDIO IRQ thread case, we can instead check the numbers of SDIO IRQs > that are