From: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
To: Feng Liu <feliu@nvidia.com>
Cc: Jason Wang <jasowang@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Bodong Wang <bodong@nvidia.com>, Feng Liu <feliu@nvidia.com>,
Jiri Pirko <jiri@nvidia.com>,
<virtualization@lists.linux-foundation.org>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] virtio_pci: Optimize virtio_pci_device structure size
Date: Wed, 17 May 2023 09:32:39 +0800 [thread overview]
Message-ID: <1684287159.5055063-1-xuanzhuo@linux.alibaba.com> (raw)
In-Reply-To: <20230516135446.16266-1-feliu@nvidia.com>
On Tue, 16 May 2023 09:54:46 -0400, Feng Liu <feliu@nvidia.com> wrote:
> Improve the size of the virtio_pci_device structure, which is commonly
> used to represent a virtio PCI device. A given virtio PCI device can
> either of legacy type or modern type, with the
> struct virtio_pci_legacy_device occupying 32 bytes and the
> struct virtio_pci_modern_device occupying 88 bytes. Make them a union,
> thereby save 32 bytes of memory as shown by the pahole tool. This
> improvement is particularly beneficial when dealing with numerous
> devices, as it helps conserve memory resources.
>
> Before the modification, pahole tool reported the following:
> struct virtio_pci_device {
> [...]
> struct virtio_pci_legacy_device ldev; /* 824 32 */
> /* --- cacheline 13 boundary (832 bytes) was 24 bytes ago --- */
> struct virtio_pci_modern_device mdev; /* 856 88 */
>
> /* XXX last struct has 4 bytes of padding */
> [...]
> /* size: 1056, cachelines: 17, members: 19 */
> [...]
> };
>
> After the modification, pahole tool reported the following:
> struct virtio_pci_device {
> [...]
> union {
> struct virtio_pci_legacy_device ldev; /* 824 32 */
> struct virtio_pci_modern_device mdev; /* 824 88 */
> }; /* 824 88 */
> [...]
> /* size: 1024, cachelines: 16, members: 18 */
> [...]
> };
>
> Signed-off-by: Feng Liu <feliu@nvidia.com>
> Reviewed-by: Jiri Pirko <jiri@nvidia.com>
Reviewed-by: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Thanks.
> ---
> drivers/virtio/virtio_pci_common.h | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/virtio/virtio_pci_common.h b/drivers/virtio/virtio_pci_common.h
> index 23112d84218f..4b773bd7c58c 100644
> --- a/drivers/virtio/virtio_pci_common.h
> +++ b/drivers/virtio/virtio_pci_common.h
> @@ -45,9 +45,10 @@ struct virtio_pci_vq_info {
> struct virtio_pci_device {
> struct virtio_device vdev;
> struct pci_dev *pci_dev;
> - struct virtio_pci_legacy_device ldev;
> - struct virtio_pci_modern_device mdev;
> -
> + union {
> + struct virtio_pci_legacy_device ldev;
> + struct virtio_pci_modern_device mdev;
> + };
> bool is_legacy;
>
> /* Where to read and clear interrupt */
> --
> 2.37.1 (Apple Git-137.1)
>
next prev parent reply other threads:[~2023-05-17 1:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 13:54 Feng Liu
2023-05-17 1:32 ` Xuan Zhuo [this message]
2023-05-17 5:23 ` Jason Wang
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=1684287159.5055063-1-xuanzhuo@linux.alibaba.com \
--to=xuanzhuo@linux.alibaba.com \
--cc=bodong@nvidia.com \
--cc=feliu@nvidia.com \
--cc=jasowang@redhat.com \
--cc=jiri@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®