Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1367929

Re: Question on rhashtable in worst-case scenario.

From Herbert Xu <herbert@gondor.apana.org.au>
Newsgroups linux.kernel
Subject Re: Question on rhashtable in worst-case scenario.
Date 2016-03-31 10:00 +0200
Message-ID <riFGi-1EX-19@gated-at.bofh.it> (permalink)
References (1 earlier) <ri4x5-mf-23@gated-at.bofh.it> <riksb-3aA-11@gated-at.bofh.it> <rirjY-87s-7@gated-at.bofh.it> <rirDm-8fh-61@gated-at.bofh.it> <riFwC-1Bm-11@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Thu, Mar 31, 2016 at 09:46:45AM +0200, Johannes Berg wrote:
>
> In this case, I think perhaps you can just patch your local system with
> the many interfaces connecting to the same AP to add the parameter
> Herbert suggested (.insecure_elasticity = true in sta_rht_params). This
> is, after all, very much a case that "normal" operation doesn't even
> get close to.

I think you should just turn it on everywhere for mac80211.  Chain
length checks simply don't make sense when you allow duplicate
keys in the hash table.

Cheers,
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Question on rhashtable in worst-case scenario. Ben Greear <greearb@candelatech.com> - 2016-03-28 22:30 +0200
  Re: Question on rhashtable in worst-case scenario. Ben Greear <greearb@candelatech.com> - 2016-03-29 18:20 +0200
    Re: Question on rhashtable in worst-case scenario. Johannes Berg <johannes@sipsolutions.net> - 2016-03-30 11:20 +0200
      Re: Question on rhashtable in worst-case scenario. Herbert Xu <herbert@gondor.apana.org.au> - 2016-03-30 16:00 +0200
        Re: Question on rhashtable in worst-case scenario. Johannes Berg <johannes@sipsolutions.net> - 2016-03-30 16:10 +0200
          Re: Question on rhashtable in worst-case scenario. Herbert Xu <herbert@gondor.apana.org.au> - 2016-03-30 16:10 +0200
      Re: Question on rhashtable in worst-case scenario. David Miller <davem@davemloft.net> - 2016-03-30 18:40 +0200
        Re: Question on rhashtable in worst-case scenario. Ben Greear <greearb@candelatech.com> - 2016-03-30 19:00 +0200
          Re: Question on rhashtable in worst-case scenario. Johannes Berg <johannes@sipsolutions.net> - 2016-03-31 09:50 +0200
            Re: Question on rhashtable in worst-case scenario. Herbert Xu <herbert@gondor.apana.org.au> - 2016-03-31 10:00 +0200
              Re: Question on rhashtable in worst-case scenario. Johannes Berg <johannes@sipsolutions.net> - 2016-03-31 17:40 +0200
                Re: Question on rhashtable in worst-case scenario. Herbert Xu <herbert@gondor.apana.org.au> - 2016-04-01 02:50 +0200
                Re: Question on rhashtable in worst-case scenario. Ben Greear <greearb@candelatech.com> - 2016-04-01 20:20 +0200
                Re: Question on rhashtable in worst-case scenario. Johannes Berg <johannes@sipsolutions.net> - 2016-04-01 23:40 +0200
                Re: Question on rhashtable in worst-case scenario. Herbert Xu <herbert@gondor.apana.org.au> - 2016-04-02 03:50 +0200
            Re: Question on rhashtable in worst-case scenario. Ben Greear <greearb@candelatech.com> - 2016-03-31 17:20 +0200
              Re: Question on rhashtable in worst-case scenario. Johannes Berg <johannes@sipsolutions.net> - 2016-03-31 17:30 +0200

csiph-web