All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Parav Pandit <parav@nvidia.com>
Cc: mst@redhat.com, jasowang@redhat.com, netdev@vger.kernel.org,
	davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
	pabeni@redhat.com, virtualization@lists.linux-foundation.org
Subject: Re: [PATCH net-next] virtio-net: Reduce debug name field size to 16 bytes
Date: Wed, 25 Jan 2023 09:30:16 +0000	[thread overview]
Message-ID: <167463901640.21491.221307420769013666.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230123035511.1122358-1-parav@nvidia.com>

Hello:

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

On Mon, 23 Jan 2023 05:55:11 +0200 you wrote:
> virtio queue index can be maximum of 65535. 16 bytes are enough to store
> the vq name with the existing string prefix.
> 
> With this change, send queue struct saves 24 bytes and receive
> queue saves whole cache line worth 64 bytes per structure
> due to saving in alignment bytes.
> 
> [...]

Here is the summary with links:
  - [net-next] virtio-net: Reduce debug name field size to 16 bytes
    https://git.kernel.org/netdev/net-next/c/d0671115869d

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-01-25  9:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-23  3:55 [PATCH net-next] virtio-net: Reduce debug name field size to 16 bytes Parav Pandit via Virtualization
2023-01-23  3:55 ` Parav Pandit
2023-01-23 14:12 ` Pavan Chebbi
2023-01-25  9:30 ` 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=167463901640.21491.221307420769013666.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jasowang@redhat.com \
    --cc=kuba@kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=parav@nvidia.com \
    --cc=virtualization@lists.linux-foundation.org \
    /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.