From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mhall@mhcomputing.net>
Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.46.186])
 by dpdk.org (Postfix) with ESMTP id BBEE99E5
 for <dev@dpdk.org>; Fri, 11 Sep 2015 19:59:56 +0200 (CEST)
Received: by mail.mhcomputing.net (Postfix, from userid 1000)
 id ABB1F80C502; Fri, 11 Sep 2015 10:58:58 -0700 (PDT)
Date: Fri, 11 Sep 2015 10:58:58 -0700
From: Matthew Hall <mhall@mhcomputing.net>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Message-ID: <20150911175858.GA2491@mhcomputing.net>
References: <1439489195-31553-1-git-send-email-vladz@cloudius-systems.com>
 <CAOYyTHZYKu6HihzVr0A7PthdhShRrB49b1qbV2wotEyYeF+K9Q@mail.gmail.com>
 <55F2F6A9.6080405@cloudius-systems.com> <3734976.j9Azrvq6io@xps13>
 <CAOYyTHbT_-dXctMkviH4hRCTcc0=X8CO+XFSmi3cyz71dDTSBQ@mail.gmail.com>
 <20150911171754.GA1572@mhcomputing.net>
 <2601191342CEEE43887BDE71AB97725836A85B76@irsmsx105.ger.corp.intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2601191342CEEE43887BDE71AB97725836A85B76@irsmsx105.ger.corp.intel.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v1] ixgbe_pmd: forbid tx_rs_thresh above 1
 for all NICs but 82598
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Sep 2015 17:59:57 -0000

On Fri, Sep 11, 2015 at 05:42:48PM +0000, Ananyev, Konstantin wrote:
> As I remember, with freebsd stack when TSO is on it was not unusual to see chains of ~30 segments. 
> That's over port with 'normal' mtu (1.5K).
> Konstantin

This makes things quite tricky, because the TSO logic itself would need to 
handle the segment generation versus the limit, as the app would not really be 
able to force TSO to change its behavior, right?

Matthew.