From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Miller <davem@davemloft.net>
Subject: Re: [PATCH RFC net-next 00/11] udp gso
Date: Wed, 18 Apr 2018 13:34:53 -0400 (EDT)
Message-ID: <20180418.133453.1026321777976247893.davem@davemloft.net>
References: <20180418123103.GC19633@oracle.com>
        <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: eric.dumazet@gmail.com, willemdebruijn.kernel@gmail.com,
        sridhar.samudrala@intel.com, netdev@vger.kernel.org,
        willemb@google.com
To: sowmini.varadhan@oracle.com
Return-path: <netdev-owner@vger.kernel.org>
Received: from shards.monkeyblade.net ([184.105.139.130]:45878 "EHLO
        shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752093AbeDRRez (ORCPT
        <rfc822;netdev@vger.kernel.org>); Wed, 18 Apr 2018 13:34:55 -0400
In-Reply-To: <20180418134706.GD19633@oracle.com>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
Date: Wed, 18 Apr 2018 09:47:06 -0400

> - in the "GSO" proposal my 2000  bytes of data are sent as *two*
>   udp packets, each of them with a unique udp header, and uh_len set
>   to 1476 (for first) and 526 (for second). The receiver has no clue
>   that they are both part of the same UDP datagram, So wire format
>   is not the same, am I mistaken?

The sender is asking for two packets and this exact packetization,
that's why they explicitly set the socket option or provide the
cmsg value.

As Eric said, this is just exchanging N sendmsg() calls with 1.