[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180420.110449.1947265114568554077.davem@davemloft.net>
Date: Fri, 20 Apr 2018 11:04:49 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: mohan.krishna.ghanta.krishnamurthy@...csson.com
Cc: tipc-discussion@...ts.sourceforge.net, jon.maloy@...csson.com,
maloy@...jonn.com, ying.xue@...driver.com, netdev@...r.kernel.org
Subject: Re: [net-next 0/3] tipc: Confgiuration of MTU for media UDP
From: GhantaKrishnamurthy MohanKrishna <mohan.krishna.ghanta.krishnamurthy@...csson.com>
Date: Thu, 19 Apr 2018 11:06:17 +0200
> Systematic measurements have shown that an emulated MTU of 14k for
> UDP bearers is the optimal value for maximal throughput. Accordingly,
> the default MTU of UDP bearers is changed to 14k.
>
> We also provide users with a fallback option from this value,
> by providing support to configure MTU for UDP bearers. The following
> options are introduced which are symmetrical to the design of
> confguring link tolerance.
>
> - Configure media with new MTU value, which will take effect on
> links going up after the moment it was configured. Alternatively,
> the bearer has to be disabled and re-enabled, for existing links to
> reflect the configured value.
>
> - Configure bearer with new MTU value, which take effect on
> running links dynamically.
>
> Please note:
> - User has to change MTU at both endpoints, otherwise the link
> will fall back to smallest MTU after a reset.
> - Failover from a link with higher MTU to a link with lower MTU
There are many negatives to using UDP in a way which causes
fragmentation, like this code now does.
But whatever, you guys can do whatever you want and get to keep the
pieces I guess :-)
Series applied.
Powered by blists - more mailing lists