From: Jiri Pirko <jiri@resnulli.us>
To: Alvaro Karsz <alvaro.karsz@solid-run.com>
Cc: Vitaly Mireyno <vmireyno@marvell.com>,
netdev@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
virtualization@lists.linux-foundation.org, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, davem@davemloft.net
Subject: Re: [patch net-next] net: virtio_net: implement exact header length guest feature
Date: Tue, 21 Feb 2023 15:27:37 +0100 [thread overview]
Message-ID: <Y/TU2W05FEIH5lGW@nanopsycho> (raw)
In-Reply-To: <CAJs=3_BW+8xL9gvUvUpFwRM_tBVvK3HY5aAQsGboN933_br9Vg@mail.gmail.com>
Tue, Feb 21, 2023 at 02:39:31PM CET, alvaro.karsz@solid-run.com wrote:
>Hi,
>
>Our device offers this feature bit as well.
>I don't have concrete numbers, but this feature will save our device a
>few cycles for every GSO packet.
Cool. I will try to include this into the patch description. Thanks!
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
WARNING: multiple messages have this Message-ID (diff)
From: Jiri Pirko <jiri@resnulli.us>
To: Alvaro Karsz <alvaro.karsz@solid-run.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Vitaly Mireyno <vmireyno@marvell.com>,
netdev@vger.kernel.org,
virtualization@lists.linux-foundation.org, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, davem@davemloft.net
Subject: Re: [patch net-next] net: virtio_net: implement exact header length guest feature
Date: Tue, 21 Feb 2023 15:27:37 +0100 [thread overview]
Message-ID: <Y/TU2W05FEIH5lGW@nanopsycho> (raw)
In-Reply-To: <CAJs=3_BW+8xL9gvUvUpFwRM_tBVvK3HY5aAQsGboN933_br9Vg@mail.gmail.com>
Tue, Feb 21, 2023 at 02:39:31PM CET, alvaro.karsz@solid-run.com wrote:
>Hi,
>
>Our device offers this feature bit as well.
>I don't have concrete numbers, but this feature will save our device a
>few cycles for every GSO packet.
Cool. I will try to include this into the patch description. Thanks!
next prev parent reply other threads:[~2023-02-21 14:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 12:15 [patch net-next] net: virtio_net: implement exact header length guest feature Jiri Pirko
2023-02-17 12:15 ` Jiri Pirko
2023-02-17 12:22 ` Michael S. Tsirkin
2023-02-17 12:22 ` Michael S. Tsirkin
2023-02-17 12:53 ` Jiri Pirko
2023-02-17 12:53 ` Jiri Pirko
2023-02-17 13:47 ` Michael S. Tsirkin
2023-02-17 13:47 ` Michael S. Tsirkin
2023-02-20 8:35 ` Jiri Pirko
2023-02-20 8:35 ` Jiri Pirko
2023-02-20 12:55 ` Michael S. Tsirkin
2023-02-20 12:55 ` Michael S. Tsirkin
2023-02-20 13:56 ` Jiri Pirko
2023-02-20 13:56 ` Jiri Pirko
2023-02-20 22:43 ` Michael S. Tsirkin
2023-02-20 22:43 ` Michael S. Tsirkin
2023-02-21 12:32 ` Jiri Pirko
2023-02-21 12:32 ` Jiri Pirko
2023-02-21 2:38 ` Jason Wang
2023-02-21 2:38 ` Jason Wang
2023-02-21 12:29 ` Jiri Pirko
2023-02-21 12:29 ` Jiri Pirko
2023-02-21 2:24 ` Jason Wang
2023-02-21 2:24 ` Jason Wang
2023-02-21 13:39 ` Alvaro Karsz
2023-02-21 13:39 ` Alvaro Karsz
2023-02-21 14:27 ` Jiri Pirko [this message]
2023-02-21 14:27 ` Jiri Pirko
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=Y/TU2W05FEIH5lGW@nanopsycho \
--to=jiri@resnulli.us \
--cc=alvaro.karsz@solid-run.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.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=vmireyno@marvell.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.