From: Sven Eckelmann <sven@open-mesh.com>
To: Johannes Berg <johannes@sipsolutions.net>
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:32:08 +0100 [thread overview]
Message-ID: <1741038.iCoNEntVIV@bentobox> (raw)
In-Reply-To: <1425639348.3339.2.camel@sipsolutions.net>
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.
Kind regards,
Sven
next prev parent reply other threads:[~2015-03-09 8:32 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 [this message]
2015-03-09 8:35 ` Johannes Berg
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=1741038.iCoNEntVIV@bentobox \
--to=sven@open-mesh.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.org \
/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).