From: Thomas Graf <tgraf-G/eBtMaohhA@public.gmane.org>
To: Bob Copeland <me-aXfl/3sk2vNUbtYUoyoikg@public.gmane.org>
Cc: linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH RFC 1/2] rhashtable: accept GFP flags in rhashtable_walk_init
Date: Tue, 1 Mar 2016 20:31:34 +0100 [thread overview]
Message-ID: <20160301193134.GA11309@pox.localdomain> (raw)
In-Reply-To: <1456708013-19590-1-git-send-email-me-aXfl/3sk2vNUbtYUoyoikg@public.gmane.org>
On 02/28/16 at 08:06pm, 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.
>
> Cc: Thomas Graf <tgraf-G/eBtMaohhA@public.gmane.org>
> Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> Signed-off-by: Bob Copeland <me-aXfl/3sk2vNUbtYUoyoikg@public.gmane.org>
rhashtable bits LGTM
Acked-by: Thomas Graf <tgraf-G/eBtMaohhA@public.gmane.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-03-01 19:31 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-03-01 13:54 ` Johannes Berg
2016-03-01 14:15 ` Bob Copeland
[not found] ` <1456708013-19590-1-git-send-email-me-aXfl/3sk2vNUbtYUoyoikg@public.gmane.org>
2016-02-29 1:06 ` [PATCH RFC 2/2] mac80211: mesh: convert path table to rhashtable Bob Copeland
2016-03-01 19:31 ` Thomas Graf [this message]
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=20160301193134.GA11309@pox.localdomain \
--to=tgraf-g/ebtmaohha@public.gmane.org \
--cc=johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=me-aXfl/3sk2vNUbtYUoyoikg@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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