netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gregory Rose <gvrose8192@gmail.com>
To: Pravin Shelar <pshelar@ovn.org>, Numan Siddique <nusiddiq@redhat.com>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>,
	ovs dev <dev@openvswitch.org>, Ben Pfaff <blp@ovn.org>
Subject: Re: [PATCH v2 net-next] net: openvswitch: Add a new action check_pkt_len
Date: Tue, 26 Mar 2019 10:40:46 -0700	[thread overview]
Message-ID: <5a7ddc47-468d-2ecd-38cc-e4163734a792@gmail.com> (raw)
In-Reply-To: <CAOrHB_C7ewjVuA4ToAgXFD4aELce4ByDQK=7Vq6X4fGh2WK7Wg@mail.gmail.com>



On 3/26/2019 9:31 AM, Pravin Shelar wrote:
> On Mon, Mar 25, 2019 at 5:44 PM <nusiddiq@redhat.com> wrote:
>> From: Numan Siddique <nusiddiq@redhat.com>
>>
>> This patch adds a new action - 'check_pkt_len' which checks the
>> packet length and executes a set of actions if the packet
>> length is greater than the specified length or executes
>> another set of actions if the packet length is lesser or equal to.
>>
>> This action takes below nlattrs
>>    * OVS_CHECK_PKT_LEN_ATTR_PKT_LEN - 'pkt_len' to check for
>>
>>    * OVS_CHECK_PKT_LEN_ATTR_ACTIONS_IF_GREATER - Nested actions
>>      to apply if the packet length is greater than the specified 'pkt_len'
>>
>>    * OVS_CHECK_PKT_LEN_ATTR_ACTIONS_IF_LESS_EQUAL - Nested
>>      actions to apply if the packet length is lesser or equal to the
>>      specified 'pkt_len'.
>>
>> The main use case for adding this action is to solve the packet
>> drops because of MTU mismatch in OVN virtual networking solution.
>> When a VM (which belongs to a logical switch of OVN) sends a packet
>> destined to go via the gateway router and if the nic which provides
>> external connectivity, has a lesser MTU, OVS drops the packet
>> if the packet length is greater than this MTU.
>>
>> With the help of this action, OVN will check the packet length
>> and if it is greater than the MTU size, it will generate an
>> ICMP packet (type 3, code 4) and includes the next hop mtu in it
>> so that the sender can fragment the packets.
>>
>> Reported-at:
>> https://mail.openvswitch.org/pipermail/ovs-discuss/2018-July/047039.html
>> Suggested-by: Ben Pfaff <blp@ovn.org>
>> Signed-off-by: Numan Siddique <nusiddiq@redhat.com>
>> CC: Gregory Rose <gvrose8192@gmail.com>
>> CC: Pravin B Shelar <pshelar@ovn.org>
>> ---
>> v1 -> v2
>> -----
>>     * Addressed the review comments.
>>       - Removed the vlan-tag length when checking the packet length
>>       - Reordered the netlink attributes
>>       - Changed the comments to use 'attribute' instead of 'action'
>>
>> Corresponding OVS patch (submitted as RFC for now)  which makes use of this action can be
>> found here - https://patchwork.ozlabs.org/patch/1059081/
>>
> Looks good to me.
> Acked-by: Pravin B Shelar <pshelar@ovn.org>

Tested-by: Greg Rose <gvrose8192@gmail.com>
Reviewed-by: Greg Rose <gvrose8192@gmail.com>

  reply	other threads:[~2019-03-26 17:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-26  0:43 [PATCH v2 net-next] net: openvswitch: Add a new action check_pkt_len nusiddiq
2019-03-26 16:31 ` Pravin Shelar
2019-03-26 17:40   ` Gregory Rose [this message]
2019-03-27 20:53 ` 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=5a7ddc47-468d-2ecd-38cc-e4163734a792@gmail.com \
    --to=gvrose8192@gmail.com \
    --cc=blp@ovn.org \
    --cc=dev@openvswitch.org \
    --cc=netdev@vger.kernel.org \
    --cc=nusiddiq@redhat.com \
    --cc=pshelar@ovn.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 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).