[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <94D0CD8314A33A4D9D801C0FE68B402958B979E6@G9W0745.americas.hpqcorp.net>
Date: Fri, 11 Jul 2014 06:02:03 +0000
From: "Elliott, Robert (Server Storage)" <Elliott@...com>
To: Jeff Moyer <jmoyer@...hat.com>
CC: Christoph Hellwig <hch@...radead.org>,
Jens Axboe <axboe@...nel.dk>,
"dgilbert@...erlog.com" <dgilbert@...erlog.com>,
James Bottomley <James.Bottomley@...senPartnership.com>,
Bart Van Assche <bvanassche@...ionio.com>,
Benjamin LaHaise <bcrl@...ck.org>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: scsi-mq V2
> -----Original Message-----
> From: linux-scsi-owner@...r.kernel.org [mailto:linux-scsi-
> owner@...r.kernel.org] On Behalf Of Elliott, Robert (Server Storage)
>
> I added some prints in aio_setup_ring and ioctx_alloc and
> rebooted. This time it took much longer to hit the problem. It
> survived dozens of ^Cs. Running a few minutes, though, IOPS
> eventually dropped. So, sometimes it happens immediately,
> sometimes it takes time to develop.
>
> I will rerun bisect-1 -2 and -3 for longer times to increase
> confidence that they didn't just appear good.
Allowing longer run times before declaring success, the problem
does appear in all of the bisect trees. I just let fio
continue to run for many minutes - no ^Cs necessary.
no-rebase: good for > 45 minutes (I will leave that running for
8 more hours)
bisect-1: bad
bisect-2: bad
bisect-3: bad
bisect-4: bad
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists