From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from 013.lax.mailroute.net (013.lax.mailroute.net [199.89.1.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 44D122F25F3 for ; Fri, 17 Jul 2026 17:06:35 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=199.89.1.16 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784307996; cv=none; b=JWKijoLkqFf61lZDGeCtDxYelkRd46vPc7fzs8KrICwuC0tlXsBV55ICsrn5wXCz7A0D7y0eYMPom/lwhdGvJGXomyBn0a19lnSx93q7s2vWJMCDndWCf52bVnCGcOoMSpv8wdIUhtRmoQqlKCfuzvwPOf4Oj4H2t+4rQXypZck= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784307996; c=relaxed/simple; bh=WRsUr8+oa3uGsserKlWWs/w0vI1bOxKed7ceNVGLbIE=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=RoXO0qfgUaLr+ZAir+xU/G4qiGAygMtgOFE21tG7m3tm6dPmTOf48LZZXVI8Tz6KXLk4bhAPQHWeggfgxcqNVYrChAoyFQUHjNZqRCSJZ21BglS/s3Ko3tNajIYwY689kk7TV5Uyl6KIXVVAVFrYw5uaayyz4YjKUJQev3XLM68= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=acm.org; spf=pass smtp.mailfrom=acm.org; dkim=pass (2048-bit key) header.d=acm.org header.i=@acm.org header.b=2MNnncFV; arc=none smtp.client-ip=199.89.1.16 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=acm.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=acm.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=acm.org header.i=@acm.org header.b="2MNnncFV" Received: from localhost (localhost [127.0.0.1]) by 013.lax.mailroute.net (Postfix) with ESMTP id 4h1xCG4yjtzlfl6P; Fri, 17 Jul 2026 17:06:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=acm.org; h= content-transfer-encoding:content-type:content-type:in-reply-to :from:from:content-language:references:subject:subject :user-agent:mime-version:date:date:message-id:received:received; s=mr01; t=1784307989; x=1786899990; bh=tx+xtzfn+syx+ZGr6WobWKJo SkVcEBXRoEYJQngWURo=; b=2MNnncFV1dqKCmys+oNr6FokU7Zusgz65yivMbS+ n2Pie4V/sMHevAxp/UqaY2vnmY2bXkHyZsogcyoC0ZVxoTdQNLB7EgBaTG41pUko WaL5PClBXyTZOJvBxj+AsYmSIQ4GqbvuhcAXKOWS4lbN61dQ4wJPKHuG6xVBEHuv xAyTSRVU/EY0E+Tkp+S6x5SkgIkbp3Nz6dDCf19/nrtdk88hZ6opzsacRs0mvPhE Gfu/qAm8I/cefsVY/p2414xQGfwfU6Sp/pesGf5svBrVwXOKj5/JcYsN6PpH2Yyg YpTnHHSR+L7Wr/boQSR/Dnq1+maJgDoGMh7CwuOVoLyHQA== X-Virus-Scanned: by MailRoute Received: from 013.lax.mailroute.net ([127.0.0.1]) by localhost (013.lax [127.0.0.1]) (mroute_mailscanner, port 10029) with LMTP id u0TF5kVScKfW; Fri, 17 Jul 2026 17:06:29 +0000 (UTC) Received: from [100.119.48.131] (unknown [104.135.180.219]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: bvanassche@acm.org) by 013.lax.mailroute.net (Postfix) with ESMTPSA id 4h1xC62b0wzlfpM6; Fri, 17 Jul 2026 17:06:26 +0000 (UTC) Message-ID: <3c29b8cb-906c-4c48-89cf-59c676900616@acm.org> Date: Fri, 17 Jul 2026 10:06:24 -0700 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v1 0/1] nvme-pci: adaptive interrupt coalescing To: Jun Zeng , kbusch@kernel.org, axboe@kernel.dk, hch@lst.de, sagi@grimberg.me Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org, andriy.shevchenko@intel.com, gang.cao@intel.com, jun.i.jin@intel.com, yong.hu@intel.com References: <20260715075703.15578-1-jun1.zeng@intel.com> Content-Language: en-US From: Bart Van Assche In-Reply-To: <20260715075703.15578-1-jun1.zeng@intel.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 7/15/26 12:57 AM, Jun Zeng wrote: > The IOPS for small IO can be significantly improved when enabling > interrupt coalescing in this case. However, in some cases (e.g., big > IO for bandwidth or latency-sensitive tests with small IO and small > queue depth), interrupt coalescing has side effects. > > Solution > ======== > > Monitor the IOPS and average queue depth of inflight IO periodically > on each NVMe drive and enable/disable interrupt coalescing > automatically without user intervention. This feature is enabled by > default and can be disabled/enabled through debugfs during runtime. An algorithm like the above can be implemented more efficiently in NVMe controller hardware than in software, isn't it? Thanks, Bart.