From owner-freebsd-current@FreeBSD.ORG Mon Oct 18 10:22:20 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D0DE16A4CE for ; Mon, 18 Oct 2004 10:22:20 +0000 (GMT) Received: from s1.vhost.cz (s1.vhost.cz [82.208.27.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1DDC743D46 for ; Mon, 18 Oct 2004 10:22:19 +0000 (GMT) (envelope-from konfer@mikulas.com) Received: (qmail 69180 invoked by uid 89); 18 Oct 2004 12:22:17 +0200 Received: from unknown (HELO localhost) (127.0.0.1) by localhost with SMTP; 18 Oct 2004 12:22:17 +0200 Received: from QMQPqq client ([127.0.0.1]) by localhost (s1.vhost.cz [127.0.0.1]) (amavisd-new, port 10628) with QMQPqq id 68862-04; Mon, 18 Oct 2004 12:22:17 +0200 (CEST) Received: from unknown (HELO mikulas.com) (jiri@mikulas.com@195.122.204.153) by s1.vhost.cz with AES256-SHA encrypted SMTP; 18 Oct 2004 12:22:17 +0200 Message-ID: <41739958.9080703@mikulas.com> Date: Mon, 18 Oct 2004 12:22:16 +0200 From: Jiri Mikulas User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040407 X-Accept-Language: cs, en, en-us MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <416DF63E.6000401@errno.com> In-Reply-To: <416DF63E.6000401@errno.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at s1.vhost.cz cc: sam@errno.com Subject: Re: net80211+atheros changes (updated) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Oct 2004 10:22:20 -0000 Hello Is there any similar version of tx rate control algorithm for wi driver for FreeBSD to solve this problem, please ? http://lists.freebsd.org/pipermail/freebsd-current/2004-May/027476.html thanks for reply Jiri >Sam Leffler wrote: > The tx rate control algorithm for the Atheros driver has broken out > into a separate module. As above you need ath_rate_onoe for the usual > algorithm. There is also an amrr algorithm that can be specified with > ath_rate_amrr.