All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Bob Copeland <me@bobcopeland.com>, linux-wireless@vger.kernel.org
Cc: 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, 01 Mar 2016 14:54:16 +0100	[thread overview]
Message-ID: <1456840456.3926.22.camel@sipsolutions.net> (raw)
In-Reply-To: <1456708013-19590-1-git-send-email-me@bobcopeland.com> (sfid-20160229_020706_258640_0460F6E4)

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.

johannes

  parent reply	other threads:[~2016-03-01 13:54 UTC|newest]

Thread overview: 8+ 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 ` Bob Copeland
2016-02-29  1:06 ` [PATCH RFC 2/2] mac80211: mesh: convert path table to rhashtable Bob Copeland
2016-02-29  1:06   ` Bob Copeland
2016-03-01 13:54 ` Johannes Berg [this message]
2016-03-01 14:15   ` [PATCH RFC 1/2] rhashtable: accept GFP flags in rhashtable_walk_init Bob Copeland
2016-03-01 19:31 ` Thomas Graf
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=1456840456.3926.22.camel@sipsolutions.net \
    --to=johannes@sipsolutions.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.