From: Stefano Brivio <sbrivio@redhat.com>
To: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Xin Long <lucien.xin@gmail.com>,
Sabrina Dubroca <sd@queasysnail.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH net 1/2] geneve, vxlan: Don't check skb_dst() twice
Date: Mon, 15 Oct 2018 13:08:30 +0200 [thread overview]
Message-ID: <20181015130830.1c177301@redhat.com> (raw)
In-Reply-To: <61596775-4b5f-884a-7a0d-d8c134bb7e8a@6wind.com>
On Mon, 15 Oct 2018 12:19:41 +0200
Nicolas Dichtel <nicolas.dichtel@6wind.com> wrote:
> Le 12/10/2018 à 23:53, Stefano Brivio a écrit :
> > Commit f15ca723c1eb ("net: don't call update_pmtu unconditionally") avoids
> > that we try updating PMTU for a non-existent destination, but didn't clean
> > up cases where the check was already explicit. Drop those redundant checks.
> Yes, I leave them to avoid calculating the new mtu value when not needed. We are
> in the xmit path.
Before 2/2 of this series, though, we call skb_dst_update_pmtu() (and
in turn dst->ops->update_pmtu()) for *every* packet with a dst, which
I'd dare saying is by far the most common case. Besides, 2/2 needs
anyway to calculate the MTU to fix a bug.
So I think this is a vast improvement overall.
If we want to improve this further and avoid any indirect calls in the
most common path, we would need to cache the MTU in the dst -- it's
probably doable, but I would fix the specific issue addressed by 2/2
first.
--
Stefano
next prev parent reply other threads:[~2018-10-15 18:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 21:53 [PATCH net 0/2] geneve, vxlan: Don't set exceptions if skb->len < mtu Stefano Brivio
2018-10-12 21:53 ` [PATCH net 1/2] geneve, vxlan: Don't check skb_dst() twice Stefano Brivio
2018-10-15 10:19 ` Nicolas Dichtel
2018-10-15 11:08 ` Stefano Brivio [this message]
2018-10-15 12:24 ` Nicolas Dichtel
2018-10-12 21:53 ` [PATCH net 2/2] geneve, vxlan: Don't set exceptions if skb->len < mtu Stefano Brivio
2018-10-15 6:01 ` Xin Long
2018-10-15 8:27 ` Stefano Brivio
2018-10-15 9:40 ` [PATCH net 0/2] " Xin Long
2018-10-18 4:51 ` David Miller
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=20181015130830.1c177301@redhat.com \
--to=sbrivio@redhat.com \
--cc=davem@davemloft.net \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=sd@queasysnail.net \
/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).