Return-path: Received: from mail-wg0-f46.google.com ([74.125.82.46]:39806 "EHLO mail-wg0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965209AbbBDMWZ convert rfc822-to-8bit (ORCPT ); Wed, 4 Feb 2015 07:22:25 -0500 Received: by mail-wg0-f46.google.com with SMTP id l2so1398386wgh.5 for ; Wed, 04 Feb 2015 04:22:23 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <1423051045.907.108.camel@edumazet-glaptop2.roam.corp.google.com> References: <1422537297.21689.15.camel@edumazet-glaptop2.roam.corp.google.com> <1422628835.21689.95.camel@edumazet-glaptop2.roam.corp.google.com> <1422903136.21689.114.camel@edumazet-glaptop2.roam.corp.google.com> <1422926330.21689.138.camel@edumazet-glaptop2.roam.corp.google.com> <1422973660.907.10.camel@edumazet-glaptop2.roam.corp.google.com> <1423051045.907.108.camel@edumazet-glaptop2.roam.corp.google.com> Date: Wed, 4 Feb 2015 13:22:23 +0100 Message-ID: (sfid-20150204_132231_056489_17A7AA13) Subject: Re: Throughput regression with `tcp: refine TSO autosizing` From: Michal Kazior To: Eric Dumazet Cc: linux-wireless , Network Development , eyalpe@dev.mellanox.co.il Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: On 4 February 2015 at 12:57, Eric Dumazet wrote: > On Wed, 2015-02-04 at 12:35 +0100, Michal Kazior wrote: > >> > (Or maybe wifi drivers should start to use skb->xmit_more as a signal to end aggregation) >> >> This could work if your firmware/device supports this kind of thing. >> To my understanding ath10k firmware doesn't. > > This is a pure software signal. You do not need firmware support. > > Idea is the following : > > Your driver gets a train of messages, coming from upper layers (TCP, IP, > qdisc) > > It can know that a packet is not the last one, by looking at > skb->xmit_more. > > Basically, aggregation logic could use this signal as a very clear > indicator you got the end of a train -> force the xmit right now. There's no way to tell ath10k firmware: "xmit right now". The firmware does all tx aggregation logic by itself. Host driver just submits a frame and hopes it'll get out soon. It's not even a tx-ring you'd expect. Each frame has a host assigned id which firmware then uses in tx completion. > To disable gso you would have to use : > > ethtool -K wlan1 gso off Oh, thanks! This works. However I can't turn it on: ; ethtool -K wlan1 gso on Could not change any device features ..so I guess it makes no sense to re-run tests because: ; ethtool -k wlan1 | grep generic tx-checksum-ip-generic: on [fixed] generic-segmentation-offload: off [requested on] generic-receive-offload: on And this seems to never change. MichaƂ