From: Johannes Berg <johannes@sipsolutions.net>
To: Sven Eckelmann <sven@open-mesh.com>
Cc: linux-wireless@vger.kernel.org, Felix Fietkau <nbd@openwrt.org>
Subject: Re: [RFC v2] [RFC] mac80211: lock rate control
Date: Mon, 09 Mar 2015 09:35:48 +0100 [thread overview]
Message-ID: <1425890148.1928.3.camel@sipsolutions.net> (raw)
In-Reply-To: <1741038.iCoNEntVIV@bentobox> (sfid-20150309_093212_837963_F79703B8)
On Mon, 2015-03-09 at 09:32 +0100, Sven Eckelmann wrote:
> On Friday 06 March 2015 11:55:48 Johannes Berg wrote:
> > > I will just add following modification to your patch and ask for a new
> > > test.
> >
> > Let me know how that goes :)
>
> I got a reply and they informed me that the test looked promising. The test
> setup didn't crash and was running stable for hours. It looks like the extra
> locking in rate_control_rate_init around ref->ops->rate_init was the missing
> part in your patch that was necessary fix the problem for them.
Great, thanks for testing.
johannes
prev parent reply other threads:[~2015-03-09 8:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 17:07 [RFC v2] [RFC] mac80211: lock rate control Johannes Berg
2015-03-06 10:47 ` Sven Eckelmann
2015-03-06 10:55 ` Johannes Berg
2015-03-09 8:32 ` Sven Eckelmann
2015-03-09 8:35 ` Johannes Berg [this message]
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=1425890148.1928.3.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.org \
--cc=sven@open-mesh.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 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.