From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sowmini Varadhan Subject: Re: [PATCH RFC net-next 00/11] udp gso Date: Tue, 17 Apr 2018 16:48:29 -0400 Message-ID: <20180417204829.GK7632@oracle.com> References: <20180417200059.30154-1-willemdebruijn.kernel@gmail.com> <20180417201557.GA4080@oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Network Development , Willem de Bruijn To: Willem de Bruijn Return-path: Received: from aserp2130.oracle.com ([141.146.126.79]:58914 "EHLO aserp2130.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751879AbeDQUs3 (ORCPT ); Tue, 17 Apr 2018 16:48:29 -0400 Content-Disposition: inline In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On (04/17/18 16:23), Willem de Bruijn wrote: > > Assuming IPv4 with an MTU of 1500 and the maximum segment > size of 1472, the receiver will see three datagrams with MSS of > 1472B, 528B and 512B. so the recvmsg will also pass up 1472, 526, 512, right? If yes, how will the recvmsg differentiate between the case (2000 byte message followed by 512 byte message) and (1472 byte message, 526 byte message, then 512 byte message), in other words, how are UDP message boundary semantics preserved? --Sowmini