qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Akihiko Odaki <akihiko.odaki@daynix.com>
To: Jason Wang <jasowang@redhat.com>
Cc: Dmitry Fleytman <dmitry.fleytman@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH] hw/net/net_tx_pkt: Fix virtio header without checksum offloading
Date: Wed, 27 Mar 2024 12:04:58 +0900	[thread overview]
Message-ID: <cc71e6c8-eca5-4ce1-9c16-8f85c6a5073e@daynix.com> (raw)
In-Reply-To: <CACGkMEsCTsQ8H6=XYMZ+8Pb9X1o19j9A4N8kiO500Dbgnw-i6g@mail.gmail.com>

On 2024/03/27 11:59, Jason Wang wrote:
> On Wed, Mar 27, 2024 at 10:53 AM Akihiko Odaki <akihiko.odaki@daynix.com> wrote:
>>
>> On 2024/03/27 11:50, Jason Wang wrote:
>>> On Tue, Mar 26, 2024 at 3:04 PM Akihiko Odaki <akihiko.odaki@daynix.com> wrote:
>>>>
>>>> On 2024/03/26 15:51, Jason Wang wrote:
>>>>> On Sun, Mar 24, 2024 at 4:32 PM Akihiko Odaki <akihiko.odaki@daynix.com> wrote:
>>>>>>
>>>>>> It is incorrect to have the VIRTIO_NET_HDR_F_NEEDS_CSUM set when
>>>>>> checksum offloading is disabled so clear the bit. Set the
>>>>>> VIRTIO_NET_HDR_F_DATA_VALID bit instead to tell the checksum is valid.
>>>>>>
>>>>>> TCP/UDP checksum is usually offloaded when the peer requires virtio
>>>>>> headers because they can instruct the peer to compute checksum. However,
>>>>>> igb disables TX checksum offloading when a VF is enabled whether the
>>>>>> peer requires virtio headers because a transmitted packet can be routed
>>>>>> to it and it expects the packet has a proper checksum. Therefore, it
>>>>>> is necessary to have a correct virtio header even when checksum
>>>>>> offloading is disabled.
>>>>>>
>>>>>> A real TCP/UDP checksum will be computed and saved in the buffer when
>>>>>> checksum offloading is disabled. The virtio specification requires to
>>>>>> set the packet checksum stored in the buffer to the TCP/UDP pseudo
>>>>>> header when the VIRTIO_NET_HDR_F_NEEDS_CSUM bit is set so the bit must
>>>>>> be cleared in that case.
>>>>>>
>>>>>> The VIRTIO_NET_HDR_F_NEEDS_CSUM bit also tells to skip checksum
>>>>>> validation. Even if checksum offloading is disabled, it is desirable to
>>>>>> skip checksum validation because the checksum is always correct. Use the
>>>>>> VIRTIO_NET_HDR_F_DATA_VALID bit to claim the validity of the checksum.
>>>>>>
>>>>>> Fixes: ffbd2dbd8e64 ("e1000e: Perform software segmentation for loopback")
>>>>>> Buglink: https://issues.redhat.com/browse/RHEL-23067
>>>>>> Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com>
>>>>>> ---
>>>>>>     hw/net/net_tx_pkt.c | 3 +++
>>>>>>     1 file changed, 3 insertions(+)
>>>>>>
>>>>>> diff --git a/hw/net/net_tx_pkt.c b/hw/net/net_tx_pkt.c
>>>>>> index 2e5f58b3c9cc..c225cf706513 100644
>>>>>> --- a/hw/net/net_tx_pkt.c
>>>>>> +++ b/hw/net/net_tx_pkt.c
>>>>>> @@ -833,6 +833,9 @@ bool net_tx_pkt_send_custom(struct NetTxPkt *pkt, bool offload,
>>>>>>
>>>>>>         if (offload || gso_type == VIRTIO_NET_HDR_GSO_NONE) {
>>>>>>             if (!offload && pkt->virt_hdr.flags & VIRTIO_NET_HDR_F_NEEDS_CSUM) {
>>>>>> +            pkt->virt_hdr.flags =
>>>>>> +                (pkt->virt_hdr.flags & ~VIRTIO_NET_HDR_F_NEEDS_CSUM) |
>>>>>> +                VIRTIO_NET_HDR_F_DATA_VALID;
>>>>>
>>>>> Why VIRTIO_NET_HDR_F_DATA_VALID is used in TX path?
>>>>
>>>> On igb, a packet sent from a PCI function may be routed to another
>>>> function. The virtio header updated here will be directly provided to
>>>> the RX path in such a case.
>>>
>>> But I meant for example net_tx_pkt_send_custom() is used in
>>> e1000e_tx_pkt_send() which is the tx path on the host.
>>>
>>> VIRTIO_NET_HDR_F_DATA_VALID is not necessary in the tx path.
>>
>> igb passes igb_tx_pkt_vmdq_callback to net_tx_pkt_send_custom().
>> igb_tx_pkt_vmdq_callback() passes the packet to its rx path for loopback.
>>
> 
> You are right, how about igb_tx_pkt_vmdq_callback()?
> 
> We probably need to tweak the name if it is only used in rx path.

igb_tx_pkt_vmdq_callback() itself is part of the tx path of a PCI 
function, and invokes the rx path of another PCI function in case of 
loopback, or triggers the transmission to the external peer.

Regards,
Akihiko Odaki

> 
> Thanks
> 
>> Regards,
>> Akihiko Odaki
>>
>>>
>>> Thanks
>>>
>>>>
>>>> Regards,
>>>> Akihiko Odaki
>>>>
>>>>>
>>>>> Thanks
>>>>>
>>>>>>                 net_tx_pkt_do_sw_csum(pkt, &pkt->vec[NET_TX_PKT_L2HDR_FRAG],
>>>>>>                                       pkt->payload_frags + NET_TX_PKT_PL_START_FRAG - 1,
>>>>>>                                       pkt->payload_len);
>>>>>>
>>>>>> ---
>>>>>> base-commit: ba49d760eb04630e7b15f423ebecf6c871b8f77b
>>>>>> change-id: 20240324-tx-c57d3c22ad73
>>>>>>
>>>>>> Best regards,
>>>>>> --
>>>>>> Akihiko Odaki <akihiko.odaki@daynix.com>
>>>>>>
>>>>>
>>>>
>>>
>>
> 


  reply	other threads:[~2024-03-27  3:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-24  8:31 [PATCH] hw/net/net_tx_pkt: Fix virtio header without checksum offloading Akihiko Odaki
2024-03-26  6:51 ` Jason Wang
2024-03-26  7:04   ` Akihiko Odaki
2024-03-27  2:50     ` Jason Wang
2024-03-27  2:52       ` Akihiko Odaki
2024-03-27  2:59         ` Jason Wang
2024-03-27  3:04           ` Akihiko Odaki [this message]
2024-03-27  3:06             ` Jason Wang
2024-03-27  3:11               ` Akihiko Odaki
2024-03-27  3:24                 ` Jason Wang
2024-03-27  4:12                   ` Akihiko Odaki

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=cc71e6c8-eca5-4ce1-9c16-8f85c6a5073e@daynix.com \
    --to=akihiko.odaki@daynix.com \
    --cc=dmitry.fleytman@gmail.com \
    --cc=jasowang@redhat.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).