linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Glenn Burkhardt <gbburkhardt@verizon.net>
Cc: Bob Copeland <me@bobcopeland.com>,
	Nick Kossifidis <mickflemm@gmail.com>,
	linux-wireless@vger.kernel.org
Subject: Re: poor performance with ath5k; reverting to ath_pci
Date: Wed, 21 Jan 2009 10:14:35 -0500	[thread overview]
Message-ID: <20090121151435.GB3643@tuxdriver.com> (raw)
In-Reply-To: <200901202238.08756.gbburkhardt@verizon.net>

On Tue, Jan 20, 2009 at 10:38:08PM -0500, Glenn Burkhardt wrote:
> On Friday 16 January 2009 10:33:13 Bob Copeland wrote:
> > On Thu, Jan 15, 2009 at 5:34 PM, Glenn Burkhardt
> >
> > <gbburkhardt@verizon.net> wrote:
> > > ath5k_pci 0000:00:07.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
> > > ath5k_pci 0000:00:07.0: registered as 'phy0'
> > > phy0: Selected rate control algorithm 'pid'
> >
> > Can you change the rate control algorithm to minstrel and retry?
> 
> I built a 2.6.28.1-9 kernel to get the minstrel code for ath5k.  The 
> kernel for Suse 11.1 is 2.6.27.7-9.  But that means that more could have 
> changed besides the rate control code.
> 
> It looks like minstrel and pid give about the same result, a bit worse that 
> the ath_pci driver right now.  Performance seems to vary from day to day.  
> I'll experiment some more, and switch transmission channels.  I'm not getting 
> the really poor performance with ath5k right now.
> 
> I haven't looked yet - is there a way to switch to 'pid' rate control without 
> rebuilding the kernel?

If you configure your kernel to include multiple rate control
algorithms then you can use the 'ieee80211_default_rc_algo' module
option for mac80211.  Of course, changing that only works if you
rmmod/insmod mac80211.

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2009-01-21 15:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-14  5:03 poor performance with ath5k; reverting to ath_pci Glenn Burkhardt
2009-01-14 13:30 ` Nick Kossifidis
2009-01-15 22:34   ` Glenn Burkhardt
2009-01-16 15:33     ` Bob Copeland
2009-01-21  3:38       ` Glenn Burkhardt
2009-01-21 15:14         ` John W. Linville [this message]
2009-01-21 18:22           ` Stefanik Gábor
2009-01-21 19:11             ` John W. Linville
2009-01-21 19:33               ` Stefanik Gábor
2009-01-21 19:34                 ` John W. Linville
2009-01-22  4:32                 ` Nick Kossifidis
2009-01-22 13:49                   ` John W. Linville
2009-01-22 14:04                     ` Johannes Berg
2009-01-22 14:17                       ` John W. Linville
2009-01-22 14:45                         ` Stefanik Gábor
2009-01-22 15:18                           ` John W. Linville
2009-01-22  2:58       ` Glenn Burkhardt
2009-01-23  7:31         ` Nick Kossifidis
2009-02-03  2:36           ` Glenn Burkhardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090121151435.GB3643@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=gbburkhardt@verizon.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=me@bobcopeland.com \
    --cc=mickflemm@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).