From: David Wragg <david@weave.works>
To: Jesse Gross <jesse@kernel.org>
Cc: David Wragg <david@weave.works>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
ovs dev <dev@openvswitch.org>, Tom Herbert <tom@herbertland.com>
Subject: Re: [PATCH net] geneve: Refine MTU limit
Date: Thu, 18 Feb 2016 16:41:17 +0000 [thread overview]
Message-ID: <86fuwq2cpe.fsf@weave.works> (raw)
In-Reply-To: <CAEh+42i628VNoXh5=vtFKzqVGeF4NqY3=GKbdNVeqmYnWK_oBg@mail.gmail.com> (Jesse Gross's message of "Tue, 16 Feb 2016 10:32:15 -0800")
Jesse Gross <jesse@kernel.org> writes:
> In addition to Tom's comment about taking into account
> dev->hard_header_len, can you please not include
> GENEVE_MAX_OPTIONS_LEN in the MTU calculation based on the discussion
> on the other thread? Otherwise, you are excluding some potentially
> valid configurations.
Addressed in v2.
David
prev parent reply other threads:[~2016-02-18 16:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 12:33 [PATCH net] geneve: Refine MTU limit David Wragg
[not found] ` <1455625999-9781-1-git-send-email-david-1SEAoVOfG6VEzL6FDj/jAg@public.gmane.org>
2016-02-16 18:32 ` Jesse Gross
2016-02-18 16:41 ` David Wragg [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=86fuwq2cpe.fsf@weave.works \
--to=david@weave.works \
--cc=dev@openvswitch.org \
--cc=jesse@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tom@herbertland.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).