From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com, jasowang@redhat.com,
virtualization@lists.linux-foundation.org,
Vitaly Mireyno <vmireyno@marvell.com>
Subject: Re: [patch net-next] net: virtio_net: implement exact header length guest feature
Date: Fri, 17 Feb 2023 08:47:36 -0500 [thread overview]
Message-ID: <20230217083915-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <Y+94418p73aUQyIn@nanopsycho>
On Fri, Feb 17, 2023 at 01:53:55PM +0100, Jiri Pirko wrote:
> Fri, Feb 17, 2023 at 01:22:01PM CET, mst@redhat.com wrote:
> >On Fri, Feb 17, 2023 at 01:15:47PM +0100, Jiri Pirko wrote:
> >> From: Jiri Pirko <jiri@nvidia.com>
> >>
> >> virtio_net_hdr_from_skb() fills up hdr_len to skb_headlen(skb).
> >>
> >> Virtio spec introduced a feature VIRTIO_NET_F_GUEST_HDRLEN which when
> >> set implicates that the driver provides the exact size of the header.
> >>
> >> The driver already complies to fill the correct value. Introduce the
> >> feature and advertise it.
> >>
> >> Signed-off-by: Jiri Pirko <jiri@nvidia.com>
> >
> >Could you add a bit of motivation just for the record?
> >Does this improve performance for some card? By how much?
> >Expected to help some future card?
>
> I can get that info, but isn't that rather something to be appended to
> the virtio-spec patch? I mean, the feature is there, this is just
> implementing it in one driver.
It is more like using it in the driver. It's not like we have to use
everything - it could be useful for e.g. dpdk but not linux.
Implementing it in the Linux driver has support costs - for example what
if there's a bug and sometimes the length is incorrect?
We'll be breaking things.
The patch was submitted by Marvell but they never bothered with
using it in Linux. I guess they are using it for something else?
CC Vitaly who put this in.
>
> >
> >thanks!
> >
> >
> >> ---
> >> drivers/net/virtio_net.c | 6 ++++--
> >> include/uapi/linux/virtio_net.h | 1 +
> >> 2 files changed, 5 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
> >> index fb5e68ed3ec2..e85b03988733 100644
> >> --- a/drivers/net/virtio_net.c
> >> +++ b/drivers/net/virtio_net.c
> >> @@ -62,7 +62,8 @@ static const unsigned long guest_offloads[] = {
> >> VIRTIO_NET_F_GUEST_UFO,
> >> VIRTIO_NET_F_GUEST_CSUM,
> >> VIRTIO_NET_F_GUEST_USO4,
> >> - VIRTIO_NET_F_GUEST_USO6
> >> + VIRTIO_NET_F_GUEST_USO6,
> >> + VIRTIO_NET_F_GUEST_HDRLEN
> >> };
> >>
> >> #define GUEST_OFFLOAD_GRO_HW_MASK ((1ULL << VIRTIO_NET_F_GUEST_TSO4) | \
> >> @@ -4213,7 +4214,8 @@ static struct virtio_device_id id_table[] = {
> >> VIRTIO_NET_F_CTRL_MAC_ADDR, \
> >> VIRTIO_NET_F_MTU, VIRTIO_NET_F_CTRL_GUEST_OFFLOADS, \
> >> VIRTIO_NET_F_SPEED_DUPLEX, VIRTIO_NET_F_STANDBY, \
> >> - VIRTIO_NET_F_RSS, VIRTIO_NET_F_HASH_REPORT, VIRTIO_NET_F_NOTF_COAL
> >> + VIRTIO_NET_F_RSS, VIRTIO_NET_F_HASH_REPORT, VIRTIO_NET_F_NOTF_COAL, \
> >> + VIRTIO_NET_F_GUEST_HDRLEN
> >>
> >> static unsigned int features[] = {
> >> VIRTNET_FEATURES,
> >> diff --git a/include/uapi/linux/virtio_net.h b/include/uapi/linux/virtio_net.h
> >> index b4062bed186a..12c1c9699935 100644
> >> --- a/include/uapi/linux/virtio_net.h
> >> +++ b/include/uapi/linux/virtio_net.h
> >> @@ -61,6 +61,7 @@
> >> #define VIRTIO_NET_F_GUEST_USO6 55 /* Guest can handle USOv6 in. */
> >> #define VIRTIO_NET_F_HOST_USO 56 /* Host can handle USO in. */
> >> #define VIRTIO_NET_F_HASH_REPORT 57 /* Supports hash report */
> >> +#define VIRTIO_NET_F_GUEST_HDRLEN 59 /* Guest provides the exact hdr_len value. */
> >> #define VIRTIO_NET_F_RSS 60 /* Supports RSS RX steering */
> >> #define VIRTIO_NET_F_RSC_EXT 61 /* extended coalescing info */
> >> #define VIRTIO_NET_F_STANDBY 62 /* Act as standby for another device
> >> --
> >> 2.39.0
> >
next prev parent reply other threads:[~2023-02-17 13:49 UTC|newest]
Thread overview: 14+ 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:22 ` Michael S. Tsirkin
2023-02-17 12:53 ` Jiri Pirko
2023-02-17 13:47 ` Michael S. Tsirkin [this message]
2023-02-20 8:35 ` Jiri Pirko
2023-02-20 12:55 ` Michael S. Tsirkin
2023-02-20 13:56 ` Jiri Pirko
2023-02-20 22:43 ` Michael S. Tsirkin
2023-02-21 12:32 ` Jiri Pirko
2023-02-21 2:38 ` Jason Wang
2023-02-21 12:29 ` Jiri Pirko
2023-02-21 2:24 ` Jason Wang
2023-02-21 13:39 ` Alvaro Karsz
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=20230217083915-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jasowang@redhat.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--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 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).