From: Greg KH <gregkh@linuxfoundation.org>
To: Eddie Chapman <eddie@ehuk.net>
Cc: Thomas Deutschmann <whissi@gentoo.org>,
stable@vger.kernel.org, davem@davemloft.net,
nicolas.dichtel@6wind.com, netdev@vger.kernel.org
Subject: Re: Request for stable 4.14.x inclusion: net: don't call update_pmtu unconditionally
Date: Sat, 28 Apr 2018 06:41:52 +0200 [thread overview]
Message-ID: <20180428044152.GD27835@kroah.com> (raw)
In-Reply-To: <7485fe73-0c33-e5b4-6c9b-c8c7a359be4a@ehuk.net>
On Fri, Apr 27, 2018 at 07:43:52PM +0100, Eddie Chapman wrote:
> On 27/04/18 19:07, Thomas Deutschmann wrote:
> > Hi Greg,
> >
> > first, we need to cherry-pick another patch first:
> > > From 52a589d51f1008f62569bf89e95b26221ee76690 Mon Sep 17 00:00:00 2001
> > > From: Xin Long <lucien.xin@gmail.com>
> > > Date: Mon, 25 Dec 2017 14:43:58 +0800
> > > Subject: [PATCH] geneve: update skb dst pmtu on tx path
> > >
> > > Commit a93bf0ff4490 ("vxlan: update skb dst pmtu on tx path") has fixed
> > > a performance issue caused by the change of lower dev's mtu for vxlan.
> > >
> > > The same thing needs to be done for geneve as well.
> > >
> > > Note that geneve cannot adjust it's mtu according to lower dev's mtu
> > > when creating it. The performance is very low later when netperfing
> > > over it without fixing the mtu manually. This patch could also avoid
> > > this issue.
> > >
> > > Signed-off-by: Xin Long <lucien.xin@gmail.com>
> > > Signed-off-by: David S. Miller <davem@davemloft.net>
>
> Oops, I completely missed that the coreos patch doesn't have the geneve hunk
> that is in the original 4.15 patch. I don't load the geneve module on my box
> hence why no problems surfaced on my machine.
>
> Thanks Thomas for the correct instructions. Ignore my message Greg, I'll
> drop back into the shadows where I belong, sorry for the noise!
Talking about patches and pointing me at them is not noise at all, don't
be sorry! :)
I'll work on this after these next kernels are released, thanks all for
the details on what needs to be done.
greg k-h
next prev parent reply other threads:[~2018-04-28 4:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-22 21:50 Request for stable 4.14.x inclusion: net: don't call update_pmtu unconditionally Thomas Deutschmann
2018-04-27 12:20 ` Thomas Deutschmann
2018-04-27 13:51 ` Greg KH
2018-04-27 14:39 ` David Miller
2018-04-27 14:45 ` Greg KH
2018-04-27 16:04 ` Eddie Chapman
2018-04-27 18:07 ` Thomas Deutschmann
2018-04-27 18:43 ` Eddie Chapman
2018-04-28 4:41 ` Greg KH [this message]
2018-04-30 18:22 ` Greg KH
2018-04-30 22:15 ` Thomas Deutschmann
2018-05-01 15:04 ` Greg KH
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=20180428044152.GD27835@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=eddie@ehuk.net \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=stable@vger.kernel.org \
--cc=whissi@gentoo.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.