[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150316041805.GA28946@gondor.apana.org.au>
Date: Mon, 16 Mar 2015 15:18:05 +1100
From: Herbert Xu <herbert@...dor.apana.org.au>
To: David Miller <davem@...emloft.net>
Cc: tgraf@...g.ch, netdev@...r.kernel.org, eric.dumazet@...il.com
Subject: Re: [v1 PATCH 0/14] rhashtable: Kill shift/Key netlink
namespace/Merge jhash
On Mon, Mar 16, 2015 at 12:01:13AM -0400, David Miller wrote:
> From: Herbert Xu <herbert@...dor.apana.org.au>
> Date: Sun, 15 Mar 2015 21:43:06 +1100
>
> > PS I'd love to kill the indirect call on the hash but I think
> > you guys need something other than jhash for sockets. Presumably
> > they are not exposed to untrusted parties. But I really wonder
> > whether that is still the case given things like namespaces where
> > even root may be untrusted.
>
> In my opinion the biggest architectural fault of rhashtables is
> these damn callbacks, look at the assembler for a simple hash
> lookup, it's disgusting.
Well if everybody used jhash the indirect call would go away...
> So essentially I think the rhashtables interface to how the keys are
> described to the user is inside out. rhashtable should just provide
> the outer-framework, and the user should provide the minute details of
> the key hashing and comparison in something that gets expanded inline.
Sure I'll try to work something out that eliminates the indirect
calls on the fast path.
However, the indirect call is still needed for rehashing but that
should be OK since rehashing is supposed to be rare.
Cheers,
--
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists