From mboxrd@z Thu Jan 1 00:00:00 1970 From: Or Gerlitz Subject: Re: [PATCH 1/9] move blk_iopoll to limit and make it generally available Date: Sun, 15 Nov 2015 11:04:11 +0200 Message-ID: References: <1447422410-20891-1-git-send-email-hch@lst.de> <1447422410-20891-2-git-send-email-hch@lst.de> <20151114070200.GA27738@lst.de> <564846E9.9070301@dev.mellanox.co.il> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: <564846E9.9070301-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org> Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Sagi Grimberg Cc: Christoph Hellwig , "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Bart Van Assche , axboe-b10kYP2dOMg@public.gmane.org, "linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Linux Kernel , Oren Duer List-Id: linux-rdma@vger.kernel.org On Sun, Nov 15, 2015 at 10:48 AM, Sagi Grimberg 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-rdma" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752592AbbKOJES (ORCPT ); Sun, 15 Nov 2015 04:04:18 -0500 Received: from mail-io0-f193.google.com ([209.85.223.193]:36687 "EHLO mail-io0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751791AbbKOJEM (ORCPT ); Sun, 15 Nov 2015 04:04:12 -0500 MIME-Version: 1.0 In-Reply-To: <564846E9.9070301@dev.mellanox.co.il> References: <1447422410-20891-1-git-send-email-hch@lst.de> <1447422410-20891-2-git-send-email-hch@lst.de> <20151114070200.GA27738@lst.de> <564846E9.9070301@dev.mellanox.co.il> Date: Sun, 15 Nov 2015 11:04:11 +0200 Message-ID: Subject: Re: [PATCH 1/9] move blk_iopoll to limit and make it generally available From: Or Gerlitz To: Sagi Grimberg Cc: Christoph Hellwig , "linux-rdma@vger.kernel.org" , Bart Van Assche , axboe@fb.com, "linux-scsi@vger.kernel.org" , Linux Kernel , Oren Duer Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Nov 15, 2015 at 10:48 AM, Sagi Grimberg 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