[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJ3xEMgvttM1D3bePz0CWhZAZ3gCSQsf_qgmq9Ny4gzK5d0bXw@mail.gmail.com>
Date: Sun, 15 Nov 2015 11:04:11 +0200
From: Or Gerlitz <gerlitz.or@...il.com>
To: Sagi Grimberg <sagig@....mellanox.co.il>
Cc: Christoph Hellwig <hch@....de>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
Bart Van Assche <bart.vanassche@...disk.com>, axboe@...com,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
Linux Kernel <linux-kernel@...r.kernel.org>,
Oren Duer <oren@...lanox.com>
Subject: Re: [PATCH 1/9] move blk_iopoll to limit and make it generally available
On Sun, Nov 15, 2015 at 10:48 AM, Sagi Grimberg
<sagig@....mellanox.co.il> wrote:
> Or is correct,
>
> I have attempted to convert iser to use blk_iopoll in the past, however
> I've seen inconsistent performance and latency skews (comparing to
> tasklets iser is using today). This was manifested in IOPs test cases
> where I ran multiple threads with higher queue-depth and not in
> sanitized pure latency (QD=1) test cases. Unfortunately I didn't have
> the time to pick it up since.
>
> I do have every intention of testing it again with this. If it still
> exist we will need to find the root-cause of it before converting
> drivers to use it.
Good, this way (inconsistent performance and latency skews) or another
(all shines up) -- please
let us know your findings, best through commenting within V > 0 the
cover letter posts of this series
--
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