From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Hall Subject: Re: [PATCH v1] ixgbe_pmd: forbid tx_rs_thresh above 1 for all NICs but 82598 Date: Fri, 11 Sep 2015 10:58:58 -0700 Message-ID: <20150911175858.GA2491@mhcomputing.net> References: <1439489195-31553-1-git-send-email-vladz@cloudius-systems.com> <55F2F6A9.6080405@cloudius-systems.com> <3734976.j9Azrvq6io@xps13> <20150911171754.GA1572@mhcomputing.net> <2601191342CEEE43887BDE71AB97725836A85B76@irsmsx105.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "dev@dpdk.org" To: "Ananyev, Konstantin" Return-path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.46.186]) by dpdk.org (Postfix) with ESMTP id BBEE99E5 for ; Fri, 11 Sep 2015 19:59:56 +0200 (CEST) Content-Disposition: inline In-Reply-To: <2601191342CEEE43887BDE71AB97725836A85B76@irsmsx105.ger.corp.intel.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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.