From: David Miller <davem@davemloft.net>
To: tlfalcon@linux.ibm.com
Cc: netdev@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH net] ibmveth: Fix max MTU limit
Date: Fri, 19 Jun 2020 20:22:29 -0700 (PDT) [thread overview]
Message-ID: <20200619.202229.791079743124441257.davem@davemloft.net> (raw)
In-Reply-To: <1592495026-27202-1-git-send-email-tlfalcon@linux.ibm.com>
From: Thomas Falcon <tlfalcon@linux.ibm.com>
Date: Thu, 18 Jun 2020 10:43:46 -0500
> The max MTU limit defined for ibmveth is not accounting for
> virtual ethernet buffer overhead, which is twenty-two additional
> bytes set aside for the ethernet header and eight additional bytes
> of an opaque handle reserved for use by the hypervisor. Update the
> max MTU to reflect this overhead.
>
> Signed-off-by: Thomas Falcon <tlfalcon@linux.ibm.com>
Applied with Fixes: tags added and queued up for -stable.
Thank you.
prev parent reply other threads:[~2020-06-20 3:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 15:43 [PATCH net] ibmveth: Fix max MTU limit Thomas Falcon
2020-06-18 15:57 ` Jakub Kicinski
2020-06-18 20:51 ` Thomas Falcon
2020-06-20 3:22 ` David Miller [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=20200619.202229.791079743124441257.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=tlfalcon@linux.ibm.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).