From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) (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 AD7B23E5589 for ; Mon, 20 Jul 2026 14:59:32 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=213.95.11.211 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784559574; cv=none; b=c2Dyvvu2X12avfVxWlyVfalnYtJ7j5jGECz4ArmPCkJooGX5cmH97aMH0wjE9h8RMKxBlJPT+HSMgXVA6IRn3s5Uwh60HFBz3yOdTf8qqGXwvPRYD0iXP3uFU7QRKzRz58S4Ur1Ryup27KYeXFMy8uo9Sz3G+OU5FZMat0MLlJw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784559574; c=relaxed/simple; bh=snBVCHu4V+oZUkx8NrhUXY91mUHxqURIC78uPVcUPQ0=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=lrjbZSN2RdaAJ+iEwsEqcL0zwHwbyZsdJPLfFAybnvk0TBmdooxk2JxoqtUSlh3hQ8w6figw2Mb8LtQ8hulW2K5r8nX3ICS0wDeYuVKL1bXGluYh9PjaZG+82atTx6NMg0/2JSG3fR3fgO11b0PYQFe+zR3Qw9iyWs1cbN2p6Kc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lst.de; spf=pass smtp.mailfrom=lst.de; arc=none smtp.client-ip=213.95.11.211 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lst.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=lst.de Received: by verein.lst.de (Postfix, from userid 2407) id 4449468C7B; Mon, 20 Jul 2026 16:59:28 +0200 (CEST) Date: Mon, 20 Jul 2026 16:59:27 +0200 From: Christoph Hellwig To: Bart Van Assche Cc: Jun Zeng , kbusch@kernel.org, axboe@kernel.dk, hch@lst.de, sagi@grimberg.me, 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 Subject: Re: [PATCH v1 0/1] nvme-pci: adaptive interrupt coalescing Message-ID: <20260720145927.GA17986@lst.de> References: <20260715075703.15578-1-jun1.zeng@intel.com> <3c29b8cb-906c-4c48-89cf-59c676900616@acm.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3c29b8cb-906c-4c48-89cf-59c676900616@acm.org> User-Agent: Mutt/1.5.17 (2007-11-01) On Fri, Jul 17, 2026 at 10:06:24AM -0700, Bart Van Assche wrote: >> 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? There is a lot of discussion on interrupt coalescing in the NVMe technical working group right now. I would suggest everyone working for a member company (and that should be everyone one the cc list here) to check that out before rushing anything.