Re: [PATCH net-next v2 16/21] net/ipv6: Add gfp_flags to route add functions

2018-04-18 Thread Eric Dumazet
On 04/18/2018 10:10 AM, David Ahern wrote: > On 4/18/18 11:06 AM, Eric Dumazet wrote: >> >> >> On 04/17/2018 05:33 PM, David Ahern wrote: >>> Most FIB entries can be added using memory allocated with GFP_KERNEL. >>> Add gfp_flags to ip6_route_add and addrconf_dst_alloc. Code paths that >>> can

Re: [PATCH net-next v2 16/21] net/ipv6: Add gfp_flags to route add functions

2018-04-18 Thread David Ahern
On 4/18/18 11:06 AM, Eric Dumazet wrote: > > > On 04/17/2018 05:33 PM, David Ahern wrote: >> Most FIB entries can be added using memory allocated with GFP_KERNEL. >> Add gfp_flags to ip6_route_add and addrconf_dst_alloc. Code paths that >> can be reached from the packet path (e.g., ndisc and

Re: [PATCH net-next v2 16/21] net/ipv6: Add gfp_flags to route add functions

2018-04-18 Thread Eric Dumazet
On 04/17/2018 05:33 PM, David Ahern wrote: > Most FIB entries can be added using memory allocated with GFP_KERNEL. > Add gfp_flags to ip6_route_add and addrconf_dst_alloc. Code paths that > can be reached from the packet path (e.g., ndisc and autoconfig) or > atomic notifiers use GFP_ATOMIC;

[PATCH net-next v2 16/21] net/ipv6: Add gfp_flags to route add functions

2018-04-17 Thread David Ahern
Most FIB entries can be added using memory allocated with GFP_KERNEL. Add gfp_flags to ip6_route_add and addrconf_dst_alloc. Code paths that can be reached from the packet path (e.g., ndisc and autoconfig) or atomic notifiers use GFP_ATOMIC; paths from user context (adding addresses and routes)