From owner-freebsd-wireless@FreeBSD.ORG Thu May 16 09:10:14 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4DAEEF3D; Thu, 16 May 2013 09:10:14 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id A93B3960; Thu, 16 May 2013 09:10:13 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:1d62:14ca:3c29:bff9]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 4BA394AC58; Thu, 16 May 2013 13:10:08 +0400 (MSK) Date: Thu, 16 May 2013 13:09:50 +0400 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <57577088.20130516130950@serebryakov.spb.ru> To: Adrian Chadd Subject: Re: [rft] improved hostap powersave / ps-poll support is now in HEAD In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 May 2013 09:10:14 -0000 Hello, Adrian. You wrote 15 =D0=BC=D0=B0=D1=8F 2013 =D0=B3., 22:34:26: AC> I've just committed my first pass of improved power save and ps-poll AC> support in AP mode to -HEAD. AC> There's a bunch of corner cases I'm trying to solve but I'd rather AC> this be in the driver now rather than later. AC> So please, update to -HEAD and give this a whirl. Let me know if AC> things are better, worse or the same. r250675, my ususal test (300 mbit AP -> Client). Looks good. First of all, it gives me stable 100-150Mbit, so it could negotiate HT rates again without TCP :) And it sustain for 600 seconds in this mode, which was impossible before. There was several such messages: May 16 12:57:31 gateway kernel: ath0: ath_tx_tid_bar_suspend: tid=3D0xfffff= f8000d82230, bar_wait=3D0, bar_tx=3D0, called May 16 12:57:31 gateway kernel: ath0: ath_tx_tid_bar_tx_ready: c4:85:08:3f:= 9e:c2: tid=3D0xffffff8000d82230 (0), bar ready May 16 12:57:31 gateway kernel: ath0: ath_tx_tid_bar_tx: c4:85:08:3f:9e:c2:= tid=3D0xffffff8000d82230, called May 16 12:57:31 gateway kernel: ath0: ath_tx_tid_bar_tx: c4:85:08:3f:9e:c2:= tid=3D0xffffff8000d82230, new BAW left edge=3D676 May 16 12:57:31 gateway kernel: ath0: ath_bar_response: c4:85:08:3f:9e:c2: = called; tap=3D0xffffff8000d7f3a0, atid=3D0xffffff8000d82230, txa_tid=3D0, a= tid->tid=3D0, status=3D0, attempts=3D1 May 16 12:57:31 gateway kernel: ath0: ath_tx_tid_bar_unsuspend: c4:85:08:3f= :9e:c2: tid=3D0xffffff8000d82230, called But no full stalls. I have dev.ath.0.debug=3D0x900000020 A lot of such messages in log when notebook is on battery (no such messages when it is on AC power): May 16 12:51:12 gateway kernel: ath0: ath_node_set_tim: c4:85:08:3f:9e:c2: = enable=3D1, enabling TIM May 16 12:51:12 gateway kernel: ath0: ath_node_powersave: c4:85:08:3f:9e:c2= : enable=3D0 May 16 12:51:12 gateway kernel: ath0: ath_node_set_tim: c4:85:08:3f:9e:c2: = enable=3D0, an_pwrsave=3D0, disabling May 16 12:51:18 gateway kernel: ath0: ath_node_powersave: c4:85:08:3f:9e:c2= : enable=3D1 May 16 12:51:18 gateway kernel: ath0: ath_node_set_tim: c4:85:08:3f:9e:c2: = enable=3D1, enabling TIM May 16 12:51:18 gateway kernel: ath0: ath_node_powersave: c4:85:08:3f:9e:c2= : enable=3D0 May 16 12:51:18 gateway kernel: ath0: ath_node_set_tim: c4:85:08:3f:9e:c2: = enable=3D0, an_pwrsave=3D0, disabling May 16 12:51:20 gateway kernel: ath0: ath_node_powersave: c4:85:08:3f:9e:c2= : enable=3D1 May 16 12:51:20 gateway kernel: ath0: ath_node_set_tim: c4:85:08:3f:9e:c2: = enable=3D1, enabling TIM May 16 12:51:20 gateway kernel: ath0: ath_node_powersave: c4:85:08:3f:9e:c2= : enable=3D0 May 16 12:51:20 gateway kernel: ath0: ath_node_set_tim: c4:85:08:3f:9e:c2: = enable=3D0, an_pwrsave=3D0, disabling May 16 12:51:21 gateway kernel: ath0: ath_node_powersave: c4:85:08:3f:9e:c2= : enable=3D1 May 16 12:51:21 gateway kernel: ath0: ath_node_set_tim: c4:85:08:3f:9e:c2: = enable=3D1, enabling TIM May 16 12:51:21 gateway kernel: ath0: ath_node_powersave: c4:85:08:3f:9e:c2= : enable=3D0 May 16 12:51:21 gateway kernel: ath0: ath_node_set_tim: c4:85:08:3f:9e:c2: = enable=3D0, an_pwrsave=3D0, disabling May 16 12:51:31 gateway kernel: ath0: ath_node_powersave: c4:85:08:3f:9e:c2= : enable=3D1 May 16 12:51:31 gateway kernel: ath0: ath_node_set_tim: c4:85:08:3f:9e:c2: = enable=3D1, enabling TIM May 16 12:51:31 gateway kernel: ath0: ath_node_powersave: c4:85:08:3f:9e:c2= : enable=3D0 May 16 12:51:31 gateway kernel: ath0: ath_node_set_tim: c4:85:08:3f:9e:c2: = enable=3D0, an_pwrsave=3D0, disabling May 16 12:51:32 gateway kernel: ath0: ath_node_powersave: c4:85:08:3f:9e:c2= : enable=3D1 May 16 12:51:32 gateway kernel: ath0: ath_node_set_tim: c4:85:08:3f:9e:c2: = enable=3D1, enabling TIM May 16 12:51:32 gateway kernel: ath0: ath_node_powersave: c4:85:08:3f:9e:c2= : enable=3D0 May 16 12:51:32 gateway kernel: ath0: ath_node_set_tim: c4:85:08:3f:9e:c2: = enable=3D0, an_pwrsave=3D0, disabling May 16 12:51:34 gateway kernel: ath0: ath_node_powersave: c4:85:08:3f:9e:c2= : enable=3D1 And sometimes it shows: May 16 13:05:52 gateway kernel: ath0: ath_node_set_tim: c4:85:08:3f:9e:c2: = enable=3D1, enabling TIM May 16 13:05:52 gateway kernel: ath0: ath_node_recv_pspoll: c4:85:08:3f:9e:= c2: leaking frame to TID 0 May 16 13:05:52 gateway kernel: ath0: ath_tx_leak_count_update: c4:85:08:3f= :9e:c2: leak count =3D 1, psq=3D1, swq=3D6, MORE=3D1 May 16 13:05:52 gateway kernel: ath0: ath_node_recv_pspoll: c4:85:08:3f:9e:= c2: leaking frame to TID 0 May 16 13:05:52 gateway kernel: ath0: ath_tx_leak_count_update: c4:85:08:3f= :9e:c2: leak count =3D 1, psq=3D1, swq=3D8, MORE=3D1 May 16 13:05:52 gateway kernel: ath0: ath_node_powersave: c4:85:08:3f:9e:c2= : enable=3D0 It is when traffic goes 100-150Mbit/s, with drops to 75-85 every ~10th second. At second test, after ~300 seconds of test in battery mode it drops to no= n-N speeds and never recovered. --=20 // Black Lion AKA Lev Serebryakov