Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933194AbaFIOJd (ORCPT ); Mon, 9 Jun 2014 10:09:33 -0400 Received: from mx0a-00082601.pphosted.com ([67.231.145.42]:9627 "EHLO mx0a-00082601.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750720AbaFIOJ2 (ORCPT ); Mon, 9 Jun 2014 10:09:28 -0400 Message-ID: <5395BFF2.2080402@fb.com> Date: Mon, 9 Jun 2014 08:08:50 -0600 From: Jens Axboe User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Ming Lei , =?UTF-8?B?TWF0aWFzIEJqw7hybGluZw==?= CC: , , , Linux Kernel Mailing List , Subject: Re: [PATCH v6] NVMe: conversion to blk-mq References: <1402057225-7312-1-git-send-email-m@bjorling.me> <1402057225-7312-2-git-send-email-m@bjorling.me> In-Reply-To: Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-Originating-IP: [192.168.57.29] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.12.52,1.0.14,0.0.0000 definitions=2014-06-09_03:2014-06-09,2014-06-09,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=fb_default_notspam policy=fb_default score=0 kscore.is_bulkscore=2.62234678416462e-13 kscore.compositescore=0 circleOfTrustscore=0 compositescore=0.324642340081358 urlsuspect_oldscore=0.324642340081358 suspectscore=0 recipient_domain_to_sender_totalscore=0 phishscore=0 bulkscore=0 kscore.is_spamscore=0 recipient_to_sender_totalscore=0 recipient_domain_to_sender_domain_totalscore=2524143 rbsscore=0.324642340081358 spamscore=0 recipient_to_sender_domain_totalscore=0 urlsuspectscore=0.9 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1406090182 X-FB-Internal: deliver Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2014-06-08 22:35, Ming Lei wrote: > On Fri, Jun 6, 2014 at 8:20 PM, Matias Bjørling wrote: >> This converts the current NVMe driver to utilize the blk-mq layer. > > Looks it can't be applied cleanly against 3.15-rc8 + Jens's for-linux > branch, when I fix the conflict manually, below failure is triggered: > > [ 487.696057] nvme 0000:00:07.0: Cancelling I/O 202 QID 1 > [ 487.699005] nvme 0000:00:07.0: Aborting I/O 202 QID 1 > [ 487.704074] nvme 0000:00:07.0: Cancelling I/O 202 QID 1 > [ 487.717881] nvme 0000:00:07.0: Aborting I/O 202 QID 1 > [ 487.736093] end_request: I/O error, dev nvme0n1, sector 91532352 > [ 487.747378] nvme 0000:00:07.0: completed id 0 twice on queue 0 > > > when running fio randread(libaio, iodepth:64) with more than 3 jobs. > > And looks no such failure when jobs is 1 or 2. It's a known issue, make sure you have this patch: http://git.kernel.dk/?p=linux-block.git;a=commit;h=f6be4fb4bcb396fc3b1c134b7863351972de081f -- Jens Axboe -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/