From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH RFC net-next 00/11] udp gso Date: Wed, 18 Apr 2018 13:40:48 -0400 (EDT) Message-ID: <20180418.134048.32104479805286488.davem@davemloft.net> References: <66ce1fb6-120f-ae49-704a-69915b317c6b@gmail.com> <20180418134706.GD19633@oracle.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: sowmini.varadhan@oracle.com, eric.dumazet@gmail.com, sridhar.samudrala@intel.com, netdev@vger.kernel.org, willemb@google.com To: willemdebruijn.kernel@gmail.com Return-path: Received: from shards.monkeyblade.net ([184.105.139.130]:45958 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751866AbeDRRku (ORCPT ); Wed, 18 Apr 2018 13:40:50 -0400 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: From: Willem de Bruijn Date: Wed, 18 Apr 2018 09:51:50 -0400 > Eric is correct. If the application sets a segment size with UDP_SEGMENT > this is an instruction to the kernel to split the payload along that border into > separate discrete datagrams. > > It does not matter what the behavior is without setting this option. If a > process wants to send a larger than MTU datagram and rely on the > kernel to fragment, then it should not set the option. +1