From: Greg KH <greg@kroah.com>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: stable@vger.kernel.org, Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH 4.19 0/2] Backport fixes for 3226b158e67c
Date: Fri, 30 Jul 2021 12:45:52 +0200 [thread overview]
Message-ID: <YQPYYCIbKhpCL9Vp@kroah.com> (raw)
In-Reply-To: <20210729184427.3202526-1-matthieu.baerts@tessares.net>
On Thu, Jul 29, 2021 at 08:44:25PM +0200, Matthieu Baerts wrote:
> Commit 3226b158e67c ("net: avoid 32 x truesize under-estimation for tiny skbs")
> introduces a ~10% performance drop when using virtio-net drivers.
>
> This commit has been backported to v4.19 in commit 669c0b5782fb and this
> performance drop is also visible there.
> Here at Tessares, we can also notice this drop with the MPTCP fork [1]
> on top of the v4.19 kernel.
>
> Eric Dumazet already fixed this issue a few months ago, see
> commit 0f6925b3e8da ("virtio_net: Do not pull payload in skb->head").
>
> Unfortunately, this patch has not been backported to < v5.4 because it
> caused issues [2]. Indeed, after having backported it, the kernel failed
> to compile because one commit was missing, see
> commit 503d539a6e41 ("virtio_net: Add XDP meta data support"). However,
> this missing commit has been added in 4.19.186 but probably because
> there were still some opened discussions [3] around
> commit 0f6925b3e8da ("virtio_net: Do not pull payload in skb->head"),
> the latter has not been backported at all in v4.19.
>
> A cherry-pick of this patch without any modification is proposed here.
> It has been validated: it fixes the original issue on v4.19 as well.
>
> Please note that there is also a fix for the fix, see
> commit 38ec4944b593 ("gro: ensure frag0 meets IP header alignment").
>
> This second fix has also not been backported because it caused issues as
> well [4]. Here, it was due to a conflict but also a compilation error
> when the conflict has been resolved. Please refer to patch 2/2 for more
> details.
>
> One last note: these two patches have also been backported and validated
> on a v4.14 release. A second series is going to be sent.
> It looks like it could be interesting to backport these two patches to
> v4.9 and v4.4 as well but unfortunately, the backport of these two
> patches fails with conflicts and I don't have any setup to validate the
> performance drop and fix with v4.9 and v4.4 kernels.
Both sets of series now queued up, thanks!
greg k-h
prev parent reply other threads:[~2021-07-30 10:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 18:44 [PATCH 4.19 0/2] Backport fixes for 3226b158e67c Matthieu Baerts
2021-07-29 18:44 ` [PATCH 4.19 1/2] virtio_net: Do not pull payload in skb->head Matthieu Baerts
2021-07-29 18:44 ` [PATCH 4.19 2/2] gro: ensure frag0 meets IP header alignment Matthieu Baerts
2021-07-30 10:45 ` Greg KH [this message]
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=YQPYYCIbKhpCL9Vp@kroah.com \
--to=greg@kroah.com \
--cc=edumazet@google.com \
--cc=matthieu.baerts@tessares.net \
--cc=stable@vger.kernel.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 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.