All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mattias Nissler <mattias.nissler@gmx.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linville@tuxdriver.com, stefano.brivio@polimi.it,
	linux-wireless@vger.kernel.org
Subject: Re: [patch 0/9] Rate control rework
Date: Mon, 17 Dec 2007 21:59:34 +0100	[thread overview]
Message-ID: <1197925174.7505.3.camel@localhost> (raw)
In-Reply-To: <1197900351.4885.41.camel@johannes.berg>


On Mon, 2007-12-17 at 15:05 +0100, Johannes Berg wrote:
> > * It seems mac80211 fails to clean up the rate control algorithm. This
> >   results in the debugfs entries created by patch 9 not being removed.
> 
> Probably a bug then, though I can't find it right now, the references
> all look balanced and if they weren't then we'd not have been able to
> rmmod rc80211_simple when it was still around. Not sure, can you try to
> see what the problem is and maybe even fix it?

Will do, after I've addressed the other issues.

> 
> It does, however, look like the whole rate control code needs a revamp.
> Looks like Jiri got busy there with krefs too without giving it too much
> thought... It looks like all that can be converted to RCU just as well
> as all the other stuff I already converted, I don't see a reason to keep
> a reference count of the rate control algorithm for each sta.

What bothers me most is the fact that we have several ways to refer to a
rate: Either we use struct ieee80211_rate pointers or indices into
local->oper_hw_mode->rates[]. This is not very consistent. Furthermore,
there is oper_hw_mode vs scan_hw_mode. So potentially even to rates[].
That sucks.

> 
> If you fix the free problem I'll take a look at fixing the locking/refs
> stuff there later.

I'll happily leave that to you, I don't have much spare time.

Mattias


  reply	other threads:[~2007-12-17 20:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-17  0:19 [patch 0/9] Rate control rework mattias.nissler
2007-12-17  0:20 ` [patch 5/9] mac80211: Introduce rate behaviour learning algorithm mattias.nissler
2007-12-17  0:20 ` [patch 9/9] mac80211: Publish rc80211_pid parameters in debugfs mattias.nissler
     [not found] ` <20071217002056.351743954@gmx.de>
2007-12-17  0:49   ` [patch 4/9] mac80211: Make PID rate control algorithm the default Johannes Berg
2007-12-17  0:50     ` Stefano Brivio
2007-12-17  0:54       ` Johannes Berg
2007-12-17  0:57         ` Stefano Brivio
2007-12-17  1:09           ` Johannes Berg
2007-12-17  9:56             ` Mattias Nissler
2007-12-17 14:48               ` John W. Linville
2007-12-17 17:42                 ` Johannes Berg
2007-12-17  9:51       ` Mattias Nissler
2007-12-17  9:54 ` [patch 0/9] Rate control rework Mattias Nissler
2007-12-17 14:05 ` Johannes Berg
2007-12-17 20:59   ` Mattias Nissler [this message]
2007-12-18 13:18     ` Johannes Berg
     [not found] ` <20071217002056.677829348@gmx.de>
2007-12-17 16:43   ` [patch 8/9] debugfs: Revamp debugfs_create_{u,x,s}{8,16,32,64} to support signed integers Johannes Berg
2007-12-17 21:05     ` Mattias Nissler

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=1197925174.7505.3.camel@localhost \
    --to=mattias.nissler@gmx.de \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=stefano.brivio@polimi.it \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.