From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 69ED3C432C0 for ; Thu, 21 Nov 2019 07:47:10 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 20B8A2088F for ; Thu, 21 Nov 2019 07:47:10 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="qNkwTgSU"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="ITV9zY7s" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 20B8A2088F Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-nvme-bounces+linux-nvme=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=aXoovd8qRzd2zHzArr6V8zLYRgkE+nIwYWmHMJvrgYY=; b=qNkwTgSUiJY8Dc OUTrofuQ27BpB0Xpf12mHyzzrRuwmqqxCqTN5VsmeRjTE/ElPsBOZ0DNINKrBYrA2OZtaCaiaHxQh B59iLsPoPXheaBOHQXjiehsuGbgwUyPiapE0JKJydzolEfHgiED8I0lQGXOZZR+2lAV4IDaX6tsjt cEz8SyVmR8tYvDeF8McX8xNycSXC1eNnbTg2Oa4fRqbK4QgfYRuLDY7+FeHvd2dlrnEXxjdjEHIvx itWrF8N88ieyvjgF91Glj9qQZeaxQrRXY2ad7R7YkEtOv5TrJZ7ipfQRtb9jMut1ejiH7OSyHgf8F UhMtJXTQH2slNA9+DVaQ==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1iXhBA-0001bY-Qf; Thu, 21 Nov 2019 07:47:04 +0000 Received: from us-smtp-delivery-1.mimecast.com ([205.139.110.120] helo=us-smtp-1.mimecast.com) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1iXhB8-0001am-2S for linux-nvme@lists.infradead.org; Thu, 21 Nov 2019 07:47:03 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1574322419; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=IscjpPDsFn05XXdOj+6dSQdRGUxBBwF8/FH6XLsr4T0=; b=ITV9zY7sG3x0QsFDqhcKEjUxhS6IMYhCNViAXMyuHNjwznLOYxngZvHgWyLahO9MwIieL/ 5B3LbRwNrTxV86fopq8181wa1hrMbYuyzQsCGAJQ7j2rqFYRSuDmCzw1Dp0TAgludP7u2+ orupRZhLtT8FIdcknTz0jS3KuAZ/wG0= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-12-Vf598A33NoOPv7TPrwPy9g-1; Thu, 21 Nov 2019 02:46:55 -0500 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 65A271883527; Thu, 21 Nov 2019 07:46:54 +0000 (UTC) Received: from ming.t460p (ovpn-8-33.pek2.redhat.com [10.72.8.33]) by smtp.corp.redhat.com (Postfix) with ESMTPS id B5331106F97D; Thu, 21 Nov 2019 07:46:47 +0000 (UTC) Date: Thu, 21 Nov 2019 15:46:43 +0800 From: Ming Lei To: Christoph Hellwig Subject: Re: [PATCH V3 0/2] nvme-pci: check CQ after batch submission for Microsoft device Message-ID: <20191121074643.GB4755@ming.t460p> References: <20191114025917.24634-1-ming.lei@redhat.com> <20191121031154.GJ24548@ming.t460p> <20191121061431.GA22886@lst.de> MIME-Version: 1.0 In-Reply-To: <20191121061431.GA22886@lst.de> User-Agent: Mutt/1.12.1 (2019-06-15) X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 X-MC-Unique: Vf598A33NoOPv7TPrwPy9g-1 X-Mimecast-Spam-Score: 0 Content-Disposition: inline X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20191120_234702_191290_278B2A44 X-CRM114-Status: GOOD ( 12.35 ) X-BeenThere: linux-nvme@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Sagi Grimberg , Long Li , linux-nvme@lists.infradead.org, Jens Axboe , Nadolski Edmund , Keith Busch Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "Linux-nvme" Errors-To: linux-nvme-bounces+linux-nvme=archiver.kernel.org@lists.infradead.org On Thu, Nov 21, 2019 at 07:14:31AM +0100, Christoph Hellwig wrote: > On Thu, Nov 21, 2019 at 11:11:54AM +0800, Ming Lei wrote: > > Hi Guys, > > > > Ping... > > I think everyone has told you that it is an invasive horrible hack > that papers of the underlying problem(s). I'm not sure what more > we can do here. The problem is that the NVMe driver applies aggressive interrupt coalescing clearly, that can be addressed exactly by this approach. Also I don't understand why you think this patch is invasive and horrible. Thanks, Ming _______________________________________________ Linux-nvme mailing list Linux-nvme@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-nvme