From: Johannes Berg <johannes@sipsolutions.net>
To: David Miller <davem@davemloft.net>, me@bobcopeland.com
Cc: linux-wireless@vger.kernel.org, tgraf@suug.ch, netdev@vger.kernel.org
Subject: Re: [PATCH 2/2] mac80211: mesh: convert path table to rhashtable
Date: Thu, 03 Mar 2016 10:37:04 +0100 [thread overview]
Message-ID: <1456997824.2044.5.camel@sipsolutions.net> (raw)
In-Reply-To: <20160302.144359.2141637165742439224.davem@davemloft.net>
On Wed, 2016-03-02 at 14:43 -0500, David Miller wrote:
> From: Bob Copeland <me@bobcopeland.com>
> Date: Wed, 2 Mar 2016 10:09:20 -0500
>
> > In the time since the mesh path table was implemented as an
> > RCU-traversable, dynamically growing hash table, a generic RCU
> > hashtable implementation was added to the kernel.
> >
> > Switch the mesh path table over to rhashtable to remove some code
> > and also gain some features like automatic shrinking.
> >
> > Cc: Thomas Graf <tgraf@suug.ch>
> > Cc: netdev@vger.kernel.org
> > Signed-off-by: Bob Copeland <me@bobcopeland.com>
>
> Johannes, feel free to take both patches via your tree, thanks.
Will do, thanks.
johannes
next prev parent reply other threads:[~2016-03-03 9:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 15:09 [PATCH 1/2] rhashtable: accept GFP flags in rhashtable_walk_init Bob Copeland
2016-03-02 15:09 ` Bob Copeland
2016-03-02 15:09 ` [PATCH 2/2] mac80211: mesh: convert path table to rhashtable Bob Copeland
2016-03-02 19:43 ` David Miller
2016-03-03 9:37 ` Johannes Berg [this message]
2016-03-03 15:26 ` [PATCH 1/2] rhashtable: accept GFP flags in rhashtable_walk_init Johannes Berg
2016-03-03 15:41 ` Bob Copeland
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=1456997824.2044.5.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=davem@davemloft.net \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.com \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.