From: "Matias Bjørling" <m@bjorling.me> To: Ming Lei <tom.leiming@gmail.com> Cc: Matthew Wilcox <willy@linux.intel.com>, Keith Busch <keith.busch@intel.com>, "Sam Bradshaw (sbradshaw)" <sbradshaw@micron.com>, Jens Axboe <axboe@fb.com>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, linux-nvme@lists.infradead.org Subject: Re: [PATCH v6] NVMe: conversion to blk-mq Date: Mon, 9 Jun 2014 08:00:45 +0200 [thread overview] Message-ID: <CAOu_J6kXB0rFJ+Z1-FcUwEVQ7dhKZseQBzVONhT1wG=41zFNGA@mail.gmail.com> (raw) In-Reply-To: <CACVXFVOieM2cT4FFJhD9MecfCLBtE3AwjCpOeGGRUcmWnN=B=A@mail.gmail.com> On Mon, Jun 9, 2014 at 6:35 AM, Ming Lei <tom.leiming@gmail.com> wrote: > On Fri, Jun 6, 2014 at 8:20 PM, Matias Bjørling <m@bjorling.me> 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. Can you try with the nvmemq_review branch at https://github.com/MatiasBjorling/linux-collab.git I'll take a look tomorrow and see if I can reproduce it. Thanks! > > Thanks, > -- > Ming Lei
WARNING: multiple messages have this Message-ID (diff)
From: m@bjorling.me (Matias Bjørling) Subject: [PATCH v6] NVMe: conversion to blk-mq Date: Mon, 9 Jun 2014 08:00:45 +0200 [thread overview] Message-ID: <CAOu_J6kXB0rFJ+Z1-FcUwEVQ7dhKZseQBzVONhT1wG=41zFNGA@mail.gmail.com> (raw) In-Reply-To: <CACVXFVOieM2cT4FFJhD9MecfCLBtE3AwjCpOeGGRUcmWnN=B=A@mail.gmail.com> On Mon, Jun 9, 2014@6:35 AM, Ming Lei <tom.leiming@gmail.com> wrote: > On Fri, Jun 6, 2014@8:20 PM, Matias Bj?rling <m@bjorling.me> 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. Can you try with the nvmemq_review branch at https://github.com/MatiasBjorling/linux-collab.git I'll take a look tomorrow and see if I can reproduce it. Thanks! > > Thanks, > -- > Ming Lei
next prev parent reply other threads:[~2014-06-09 6:00 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-06 12:20 [PATCH v6] conversion to blk-mq Matias Bjørling 2014-06-06 12:20 ` Matias Bjørling 2014-06-06 12:20 ` [PATCH v6] NVMe: " Matias Bjørling 2014-06-06 12:20 ` Matias Bjørling 2014-06-09 4:35 ` Ming Lei 2014-06-09 4:35 ` Ming Lei 2014-06-09 6:00 ` Matias Bjørling [this message] 2014-06-09 6:00 ` Matias Bjørling 2014-06-09 7:50 ` Ming Lei 2014-06-09 7:50 ` Ming Lei 2014-06-09 7:53 ` Ming Lei 2014-06-09 7:53 ` Ming Lei 2014-06-09 10:40 ` Ming Lei 2014-06-09 10:40 ` Ming Lei 2014-06-12 0:58 ` Ming Lei 2014-06-12 0:58 ` Ming Lei 2014-06-09 14:08 ` Jens Axboe 2014-06-09 14:08 ` Jens Axboe 2014-06-09 14:59 ` Christoph Hellwig 2014-06-09 14:59 ` Christoph Hellwig 2014-06-09 15:27 ` Jens Axboe 2014-06-09 15:27 ` Jens Axboe 2014-06-09 15:35 ` Ming Lei 2014-06-09 15:35 ` Ming Lei 2014-06-10 11:35 ` Christoph Hellwig 2014-06-10 11:35 ` Christoph Hellwig 2014-06-10 11:55 ` Ming Lei 2014-06-10 11:55 ` Ming Lei 2014-06-10 12:40 ` Christoph Hellwig 2014-06-10 12:40 ` Christoph Hellwig 2014-06-09 15:07 ` Ming Lei 2014-06-09 15:07 ` Ming Lei 2014-06-09 15:10 ` Jens Axboe 2014-06-09 15:10 ` Jens Axboe 2014-06-09 15:15 ` Ming Lei 2014-06-09 15:15 ` Ming Lei 2014-06-09 15:40 ` Jens Axboe 2014-06-09 15:40 ` Jens Axboe 2014-06-10 19:42 ` Matias Bjørling 2014-06-10 19:42 ` Matias Bjørling
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CAOu_J6kXB0rFJ+Z1-FcUwEVQ7dhKZseQBzVONhT1wG=41zFNGA@mail.gmail.com' \ --to=m@bjorling.me \ --cc=axboe@fb.com \ --cc=keith.busch@intel.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-nvme@lists.infradead.org \ --cc=sbradshaw@micron.com \ --cc=tom.leiming@gmail.com \ --cc=willy@linux.intel.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.