From: "Алексей Болдырев" <devel-net-ne-vlezay80@yandex•ru>
To: Joe Stringer <joe@ovn•org>
Cc: David Ahern <dsahern@gmail•com>, netdev <netdev@vger•kernel.org>
Subject: Re: Maximum MPLS labels on Linux network stack
Date: Thu, 04 May 2017 00:29:05 +0300 [thread overview]
Message-ID: <454271493846945@web51g.yandex.ru> (raw)
In-Reply-To: <CAPWQB7HrbCVLEjaR0hObPTxrDg8qyfZo-3iYLe=NVzuPTOLxCQ@mail.gmail.com>
As I understand it, it's enough to just set the variable in the source
#define FLOW_MAX_MPLS_LABELS 3
on
#define FLOW_MAX_MPLS_LABELS 7
Or is there somehow still pitfalls?
04.05.2017, 00:22, "Joe Stringer" <joe@ovn•org>:
> On 3 May 2017 at 14:19, Алексей Болдырев
> <devel-net-ne-vlezay80@yandex•ru> wrote:
>> Is it possible to increase this limit in OpenVswitch?
>
> Yes.
next prev parent reply other threads:[~2017-05-03 21:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 17:33 Maximum MPLS labels on Linux network stack Алексей Болдырев
2017-05-03 18:14 ` David Ahern
2017-05-03 20:21 ` Joe Stringer
2017-05-03 21:19 ` Алексей Болдырев
2017-05-03 21:22 ` Joe Stringer
2017-05-03 21:29 ` Алексей Болдырев [this message]
2017-05-03 21:46 ` Joe Stringer
2017-05-04 2:22 ` David Ahern
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=454271493846945@web51g.yandex.ru \
--to=devel-net-ne-vlezay80@yandex$(echo .)ru \
--cc=dsahern@gmail$(echo .)com \
--cc=joe@ovn$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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