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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7D6BDC001DE for ; Wed, 2 Aug 2023 04:10:33 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231416AbjHBEKa (ORCPT ); Wed, 2 Aug 2023 00:10:30 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44572 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230400AbjHBEK1 (ORCPT ); Wed, 2 Aug 2023 00:10:27 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9779BFE for ; Tue, 1 Aug 2023 21:10:26 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 2D75F617B8 for ; Wed, 2 Aug 2023 04:10:26 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPS id 87B80C433CB; Wed, 2 Aug 2023 04:10:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1690949425; bh=CJd8mXJemcfMooHI8Zob7wc84xGAUX83lz4AkkEYPn0=; h=Subject:From:Date:References:In-Reply-To:To:Cc:From; b=RHqxP+1Pf+J/w1tyl+oG3Hw34WIGv4VviX6VcXmfi7SjAXq8kzHmIIuH9bxUnhxNR l3CV6ckJ3WdtvxDa4LbRgVPLsQQR4dcIkG3etf6UyYGcxjsMGEldWDsjDPRjnf68AV 8ieGB/Yo3U0QTUHPgXCjRghletohS7Jxbgqu96HbLRZiEF8kACAEN2NqmWAR7hEk+P nr9nPs/H/L+b1DdtY9x4QLkv4WqXOaCPFzyTzpAVjQ9RRkaXPsD8CXycu+0yf55iMk LW+Tfl7qvzkMDJ6mHiPfgdHAhislOt4nQWr76i2h4dMEKE4Vl4d7bllvTWt06vgY8L ABS7y6UxUxLqA== Received: from aws-us-west-2-korg-oddjob-1.ci.codeaurora.org (localhost.localdomain [127.0.0.1]) by aws-us-west-2-korg-oddjob-1.ci.codeaurora.org (Postfix) with ESMTP id 718AAC691F0; Wed, 2 Aug 2023 04:10:25 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [PATCH net-next V5 0/3] virtio_net: add per queue interrupt coalescing support From: patchwork-bot+netdevbpf@kernel.org Message-Id: <169094942545.31458.1603309182544531344.git-patchwork-notify@kernel.org> Date: Wed, 02 Aug 2023 04:10:25 +0000 References: <20230731070656.96411-1-gavinl@nvidia.com> In-Reply-To: <20230731070656.96411-1-gavinl@nvidia.com> To: Gavin Li Cc: mst@redhat.com, jasowang@redhat.com, xuanzhuo@linux.alibaba.com, davem@davemloft.net, edumazet@google.com, kuba@kernel.org, pabeni@redhat.com, ast@kernel.org, daniel@iogearbox.net, hawk@kernel.org, john.fastabend@gmail.com, jiri@nvidia.com, dtatulea@nvidia.com, gavi@nvidia.com, virtualization@lists.linux-foundation.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, bpf@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello: This series was applied to netdev/net-next.git (main) by Jakub Kicinski : On Mon, 31 Jul 2023 10:06:53 +0300 you wrote: > Currently, coalescing parameters are grouped for all transmit and receive > virtqueues. This patch series add support to set or get the parameters for > a specified virtqueue. > > When the traffic between virtqueues is unbalanced, for example, one virtqueue > is busy and another virtqueue is idle, then it will be very useful to > control coalescing parameters at the virtqueue granularity. > > [...] Here is the summary with links: - [net-next,V5,1/3] virtio_net: extract interrupt coalescing settings to a structure https://git.kernel.org/netdev/net-next/c/308d7982dcdc - [net-next,V5,2/3] virtio_net: support per queue interrupt coalesce command https://git.kernel.org/netdev/net-next/c/394bd87764b6 - [net-next,V5,3/3] virtio_net: enable per queue interrupt coalesce feature https://git.kernel.org/netdev/net-next/c/8af3bf668382 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html