From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Nick Piggin <npiggin@suse.de>
Cc: David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-netdev@vger.kernel.org, josh@freedesktop.org
Subject: Re: [patch][rfc] ddds: "dynamic dynamic data structure" algorithm, for adaptive dcache hash table sizing
Date: Tue, 7 Oct 2008 20:12:45 -0700 [thread overview]
Message-ID: <20081008031245.GC7101@linux.vnet.ibm.com> (raw)
In-Reply-To: <20081008024813.GC6499@wotan.suse.de>
On Wed, Oct 08, 2008 at 04:48:13AM +0200, Nick Piggin wrote:
> On Tue, Oct 07, 2008 at 02:08:25PM -0700, David Miller wrote:
> > From: Nick Piggin <npiggin@suse.de>
> > Date: Tue, 7 Oct 2008 08:48:34 +0200
> >
> > > I'm cc'ing netdev because Dave did express some interest in using this for
> > > some networking hashes, and network guys in general are pretty cluey when it
> > > comes to hashes and such ;)
> >
> > Interesting stuff.
> >
> > Paul, many months ago, forwarded to me a some work done by Josh
> > Triplett called "rcuhashbash" which had similar objectives. He did
> > post it to linux-kernel, and perhaps even your ideas are inspired by
> > his work, I don't know. :-)
>
> Hmm yes I did see that. It's not too similar, as it focuses on re-keying
> an existing element into the same hash table. ddds can't do that kind of
> thing (the underlying data structure isn't visible to the algorithm, so
> it can't exactly modify data structures in-place), although in another
> sense it is more general because the transfer function could transfer
> items into another hash table and re-key them as it goes (if it did that,
> it could probably use Josh's "atomic" re-keying algorithm too).
>
> But largely it does seem like they are orthogonal (if I'm reading
> rcuhashbash correctly).
IIRC, one of the weaknesses of rcuhashbash was that the elements had
to be copied in some cases. Josh has been working on a variant that
(hopefully) allows elements to be moved without copying, as is required
by dcache.
Thanx, Paul
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-10-08 3:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 6:48 Nick Piggin
2008-10-07 7:02 ` [patch][rfc] ddds: "dynamic dynamic data structure" algorithm, for adaptive dcache hash table sizing (resend) Nick Piggin
2008-10-07 7:18 ` Christoph Hellwig
2008-10-07 7:53 ` Nick Piggin
2008-10-07 21:06 ` David Miller, Nick Piggin
2008-10-07 15:37 ` Mikael Pettersson
2008-10-07 16:39 ` Nick Piggin
2008-10-07 7:37 ` Eric Dumazet
2008-10-07 8:06 ` Nick Piggin
2008-10-07 21:05 ` David Miller, Nick Piggin
2008-10-08 2:38 ` Nick Piggin
2008-10-07 21:08 ` [patch][rfc] ddds: "dynamic dynamic data structure" algorithm, for adaptive dcache hash table sizing David Miller, Nick Piggin
2008-10-08 2:48 ` Nick Piggin
2008-10-08 3:12 ` Paul E. McKenney [this message]
2008-10-08 3:27 ` Nick Piggin
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=20081008031245.GC7101@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=josh@freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-netdev@vger.kernel.org \
--cc=npiggin@suse.de \
/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