netdev - Re: [PATCH v2 net-next] net: extend net

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20131103.231936.1376432697924210356.davem@davemloft.net>
Date:	Sun, 03 Nov 2013 23:19:36 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	eric.dumazet@...il.com
Cc:	joby.poriyath@...rix.com, bhutchings@...arflare.com,
	netdev@...r.kernel.org, wei.liu2@...rix.com,
	ian.campbell@...rix.com, xen-devel@...ts.xen.org,
	andrew.bennieston@...rix.com, david.vrabel@...rix.com,
	malcolm.crossley@...rix.com
Subject: Re: [PATCH v2 net-next] net: extend net_device allocation to
 vmalloc()

From: Eric Dumazet <eric.dumazet@...il.com>
Date: Wed, 30 Oct 2013 13:10:44 -0700

> From: Eric Dumazet <edumazet@...gle.com>
> 
> Joby Poriyath provided a xen-netback patch to reduce the size of
> xenvif structure as some netdev allocation could fail under
> memory pressure/fragmentation.
> 
> This patch is handling the problem at the core level, allowing
> any netdev structures to use vmalloc() if kmalloc() failed.
> 
> As vmalloc() adds overhead on a critical network path, add __GFP_REPEAT
> to kzalloc() flags to do this fallback only when really needed.
> 
> Signed-off-by: Eric Dumazet <edumazet@...gle.com>
> Reported-by: Joby Poriyath <joby.poriyath@...rix.com>
> Cc: Ben Hutchings <bhutchings@...arflare.com>
> ---
> v2: change the Documentation to point to alloc_netdev_mqs()
>     instead of kmalloc()/vzalloc(), from Ben

Looks good, applied, thanks Eric.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html