public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Gavin Li <gavinl@nvidia.com>
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
Subject: Re: [PATCH net-next V5 0/3] virtio_net: add per queue interrupt coalescing support
Date: Wed, 02 Aug 2023 04:10:25 +0000	[thread overview]
Message-ID: <169094942545.31458.1603309182544531344.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230731070656.96411-1-gavinl@nvidia.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

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



      parent reply	other threads:[~2023-08-02  4:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-31  7:06 [PATCH net-next V5 0/3] virtio_net: add per queue interrupt coalescing support Gavin Li
2023-07-31  7:06 ` [PATCH net-next V5 1/3] virtio_net: extract interrupt coalescing settings to a structure Gavin Li
2023-07-31  7:06 ` [PATCH net-next V5 2/3] virtio_net: support per queue interrupt coalesce command Gavin Li
2023-07-31  7:06 ` [PATCH net-next V5 3/3] virtio_net: enable per queue interrupt coalesce feature Gavin Li
2023-08-02  4:10 ` patchwork-bot+netdevbpf [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=169094942545.31458.1603309182544531344.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=dtatulea@nvidia.com \
    --cc=edumazet@google.com \
    --cc=gavi@nvidia.com \
    --cc=gavinl@nvidia.com \
    --cc=hawk@kernel.org \
    --cc=jasowang@redhat.com \
    --cc=jiri@nvidia.com \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=xuanzhuo@linux.alibaba.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox