All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Heng Qi <hengqi@linux.alibaba.com>
Cc: netdev@vger.kernel.org,
	virtualization@lists.linux-foundation.org, jasowang@redhat.com,
	mst@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
Subject: Re: [PATCH v3 0/6] virtio-net: Fix and update interrupt moderation
Date: Wed, 11 Oct 2023 06:20:26 +0000	[thread overview]
Message-ID: <169700522610.29366.5456934830457693913.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1696745452.git.hengqi@linux.alibaba.com>

Hello:

This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:

On Sun,  8 Oct 2023 14:27:38 +0800 you wrote:
> The setting of virtio coalescing parameters involves all-queues and
> per queue, so we must be careful to synchronize the two.
> 
> Regarding napi_tx switching, this patch set is not only
> compatible with the previous way of using tx-frames to switch napi_tx,
> but also improves the user experience when setting interrupt parameters.
> 
> [...]

Here is the summary with links:
  - [v3,1/6] virtio-net: initially change the value of tx-frames
    https://git.kernel.org/netdev/net-next/c/3014a0d54820
  - [v3,2/6] virtio-net: fix mismatch of getting tx-frames
    https://git.kernel.org/netdev/net-next/c/134674c1877b
  - [v3,3/6] virtio-net: consistently save parameters for per-queue
    https://git.kernel.org/netdev/net-next/c/e9420838ab4f
  - [v3,4/6] virtio-net: fix per queue coalescing parameter setting
    https://git.kernel.org/netdev/net-next/c/bfb2b3609162
  - [v3,5/6] virtio-net: fix the vq coalescing setting for vq resize
    https://git.kernel.org/netdev/net-next/c/f61fe5f081cf
  - [v3,6/6] virtio-net: a tiny comment update
    https://git.kernel.org/netdev/net-next/c/c4e33cf2611b

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-10-11  6:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-08  6:27 [PATCH v3 0/6] virtio-net: Fix and update interrupt moderation Heng Qi
2023-10-08  6:27 ` [PATCH v3 1/6] virtio-net: initially change the value of tx-frames Heng Qi
2023-10-08  6:27 ` [PATCH v3 2/6] virtio-net: fix mismatch of getting tx-frames Heng Qi
2023-10-08  6:27 ` [PATCH v3 3/6] virtio-net: consistently save parameters for per-queue Heng Qi
2023-10-08  6:27 ` [PATCH v3 4/6] virtio-net: fix per queue coalescing parameter setting Heng Qi
2023-10-08  6:27 ` [PATCH v3 5/6] virtio-net: fix the vq coalescing setting for vq resize Heng Qi
2023-10-08  6:27 ` [PATCH v3 6/6] virtio-net: a tiny comment update Heng Qi
2023-10-11  6:20 ` 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=169700522610.29366.5456934830457693913.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ast@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hawk@kernel.org \
    --cc=hengqi@linux.alibaba.com \
    --cc=jasowang@redhat.com \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.