From: Bob Copeland <me@bobcopeland.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, Thomas Graf <tgraf@suug.ch>,
netdev@vger.kernel.org
Subject: Re: [PATCH RFC 1/2] rhashtable: accept GFP flags in rhashtable_walk_init
Date: Tue, 1 Mar 2016 09:15:11 -0500 [thread overview]
Message-ID: <20160301141511.GC19848@localhost> (raw)
In-Reply-To: <1456840456.3926.22.camel@sipsolutions.net>
On Tue, Mar 01, 2016 at 02:54:16PM +0100, Johannes Berg wrote:
> On Sun, 2016-02-28 at 20:06 -0500, Bob Copeland wrote:
> > In certain cases, the 802.11 mesh pathtable code wants to
> > iterate over all of the entries in the forwarding table from
> > the receive path, which is inside an RCU read-side critical
> > section. Enable walks inside atomic sections by allowing
> > GFP_ATOMIC allocations for the walker state.
> >
> > Change all existing callsites to pass in GFP_KERNEL.
>
> Both look fine to me.
>
> I see you have more patches for mesh, so this probably can't go through
> net-next tree directly.
Yeah, these two are on top of the other mesh path table changes.
So either both of these could go via mac80211-next or we could do the
1/2 in net-next and wait to apply 2/2 in mac80211-next. Whatever works
for you guys.
--
Bob Copeland %% http://bobcopeland.com/
next prev parent reply other threads:[~2016-03-01 14:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 1:06 [PATCH RFC 1/2] rhashtable: accept GFP flags in rhashtable_walk_init Bob Copeland
2016-02-29 1:06 ` [PATCH RFC 2/2] mac80211: mesh: convert path table to rhashtable Bob Copeland
2016-03-01 13:54 ` [PATCH RFC 1/2] rhashtable: accept GFP flags in rhashtable_walk_init Johannes Berg
2016-03-01 14:15 ` Bob Copeland [this message]
2016-03-01 19:31 ` Thomas Graf
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=20160301141511.GC19848@localhost \
--to=me@bobcopeland.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--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 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).