From: Johannes Berg <johannes@sipsolutions.net>
To: greearb@candelatech.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: Ensure no limits on station rhashtable.
Date: Tue, 05 Apr 2016 11:08:04 +0200 [thread overview]
Message-ID: <1459847284.18188.19.camel@sipsolutions.net> (raw)
In-Reply-To: <1459545211-11517-1-git-send-email-greearb@candelatech.com>
On Fri, 2016-04-01 at 14:13 -0700, greearb@candelatech.com wrote:
> From: Ben Greear <greearb@candelatech.com>
>
> By default, the rhashtable logic will fail to insert
> objects if the key-chains are too long and un-balanced.
>
> In the degenerate case where mac80211 is creating many
> station vdevs connected to the same peer, this case can
> be hit.
>
> So, set insecure_elasticity to true to allow chains to grow
> as long as needed.
>
Applied.
johannes
prev parent reply other threads:[~2016-04-05 9:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 21:13 [PATCH] mac80211: Ensure no limits on station rhashtable greearb
2016-04-05 9:08 ` 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=1459847284.18188.19.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.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).