From: Jared Rossi <jrossi@linux.ibm.com>
To: Zhuoying Cai <zycai@linux.ibm.com>,
qemu-devel@nongnu.org, qemu-s390x@nongnu.org
Cc: mst@redhat.com, borntraeger@linux.ibm.com, jjherne@linux.ibm.com,
cohuck@redhat.com, farman@linux.ibm.com, mjrosato@linux.ibm.com,
pasic@linux.ibm.com, farosas@suse.de, lvivier@redhat.com,
pbonzini@redhat.com, jdaley@linux.ibm.com
Subject: Re: [PATCH v3 2/8] pc-bios/s390-ccw: Add dynamic net header size handling
Date: Mon, 21 Sep 2026 09:47:07 -0400 [thread overview]
Message-ID: <078f5d97-2dde-49e5-af52-6053cd418b6d@linux.ibm.com> (raw)
In-Reply-To: <20260914193438.526407-3-zycai@linux.ibm.com>
On 9/14/26 3:34 PM, Zhuoying Cai wrote:
> The virtio-net device used a fixed header size that did not account for
> the num_buffers field used in VirtIO 1.0.
>
> Use dynamic header sizing: 10 bytes for legacy mode and 12 bytes for
> VirtIO 1.0. This ensures correct packet handling across different
> VirtIO configurations.
>
> The VirtioNetHdr and VirtioNetHdrMrgRxbuf structures replicate the
> same field layout as struct virtio_net_hdr and struct
> virtio_net_hdr_mrg_rxbuf defined in inux/uapi/linux/virtio_net.h.
>
> Signed-off-by: Zhuoying Cai <zycai@linux.ibm.com>
> ---
With the correction to the file path that Christian pointed out,
Reviewed-by: Jared Rossi <jrossi@linux.ibm.com>
next prev parent reply other threads:[~2026-09-21 13:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 19:34 [PATCH v3 0/8] s390x: Add support for virtio-net-pci boot device Zhuoying Cai
2026-09-14 19:34 ` [PATCH v3 1/8] pc-bios/s390-ccw: Move CCW net setup to virtio-ccw Zhuoying Cai
2026-09-14 19:34 ` [PATCH v3 2/8] pc-bios/s390-ccw: Add dynamic net header size handling Zhuoying Cai
2026-09-18 7:50 ` Christian Borntraeger
2026-09-21 13:47 ` Jared Rossi [this message]
2026-09-22 21:34 ` Matthew Rosato
2026-09-14 19:34 ` [PATCH v3 3/8] pc-bios/s390-ccw: Introduce virtio_tswap helpers Zhuoying Cai
2026-09-14 19:34 ` [PATCH v3 4/8] pc-bios/s390-ccw: Add support for virtio-net-pci IPL Zhuoying Cai
2026-09-22 15:35 ` Joshua Daley
2026-09-22 15:51 ` Zhuoying Cai
2026-09-22 21:35 ` Matthew Rosato
2026-09-23 13:04 ` Jared Rossi
2026-09-14 19:34 ` [PATCH v3 5/8] hw/virtio: Add "loadparm" property to virtio net PCI devices booting on s390x Zhuoying Cai
2026-09-22 22:03 ` Matthew Rosato
2026-09-14 19:34 ` [PATCH v3 6/8] tests/qtest: Check s390x boot device support in pxe-test.c Zhuoying Cai
2026-09-22 19:34 ` Joshua Daley
2026-09-23 0:27 ` Matthew Rosato
2026-09-14 19:34 ` [PATCH v3 7/8] tests/qtest: Add s390x virtio net PCI test to pxe-test.c Zhuoying Cai
2026-09-22 16:06 ` Joshua Daley
2026-09-22 19:37 ` Joshua Daley
2026-09-23 0:27 ` Matthew Rosato
2026-09-14 19:34 ` [PATCH v3 8/8] tests/functional/s390x: Add tests for virtio net PCI in test_pxelinux.py Zhuoying Cai
2026-09-23 1:01 ` Matthew Rosato
2026-09-22 21:33 ` [PATCH v3 0/8] s390x: Add support for virtio-net-pci boot device Matthew Rosato
2026-09-23 1:01 ` Matthew Rosato
2026-09-23 14:20 ` Zhuoying Cai
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=078f5d97-2dde-49e5-af52-6053cd418b6d@linux.ibm.com \
--to=jrossi@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=farman@linux.ibm.com \
--cc=farosas@suse.de \
--cc=jdaley@linux.ibm.com \
--cc=jjherne@linux.ibm.com \
--cc=lvivier@redhat.com \
--cc=mjrosato@linux.ibm.com \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=zycai@linux.ibm.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.