[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <577F1AD7.8040800@gmail.com>
Date: Fri, 8 Jul 2016 12:15:35 +0900
From: Masashi Honma <masashi.honma@...il.com>
To: Eric Dumazet <eric.dumazet@...il.com>
Cc: netdev@...r.kernel.org, netfilter-devel@...r.kernel.org,
linux-wireless@...r.kernel.org, linux-rdma@...r.kernel.org,
linux-audit@...hat.com, cluster-devel@...hat.com,
davem@...emloft.net, johannes@...solutions.net,
pablo@...filter.org, kaber@...sh.net, kadlec@...ckhole.kfki.hu,
dledford@...hat.com, sean.hefty@...el.com,
hal.rosenstock@...il.com, paul@...l-moore.com, eparis@...hat.com,
zbr@...emap.net, pshelar@...ira.com, ccaulfie@...hat.com,
teigland@...hat.com, bsingharora@...il.com
Subject: Re: [RFC 5/7] net: Add allocation flag to rtnl_unicast()
On 2016年07月08日 11:56, Eric Dumazet wrote:
>
> Managing to mix GFP_ATOMIC and GFP_KERNEL almost randomly as you did in
> this patch is definitely not good.
>
> Further more, RTNL is a mutex, held in control path, designed to allow
> schedules and waiting for memory under pressure.
>
> We do not want to encourage GFP_ATOMIC usage in control path.
>
> Your patch series gives the wrong signal to developers.
>
>
>
Thanks for comment.
I have selected GFP flags based on existing code.
I have selected GFP_ATOMIC in inet6_netconf_get_devconf() because
skb was allocated with GFP_ATOMIC.
I have used GFP_KERNEL in inet6_rtm_getaddr() by same reason.
> I will send a patch against net/ipv4/devinet.c so that we remove
> GFP_ATOMIC usage there.
Thanks. I will modify my patch based on your new code.
Powered by blists - more mailing lists