linux-kernel - Re: [RFC v2] percpu: Add a separate function to merge free areas

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.11.1412041426230.14577@gentwo.org>
Date:	Thu, 4 Dec 2014 14:28:10 -0600 (CST)
From:	Christoph Lameter <cl@...ux.com>
To:	Leonard Crestez <lcrestez@...acom.com>
cc:	Tejun Heo <tj@...nel.org>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org, Sorin Dumitru <sdumitru@...acom.com>
Subject: Re: [RFC v2] percpu: Add a separate function to merge free areas

On Thu, 4 Dec 2014, Leonard Crestez wrote:

> Yes, we are actually experiencing issues with this. We create lots of virtual
> net_devices and routes, which means lots of percpu counters/pointers. In particular
> we are getting worse performance than in older kernels because the net_device refcnt
> is now a percpu counter. We could turn that back into a single integer but this
> would negate an upstream optimization.

Well this is not a common use case and that is not what the per cpu
allocator was designed for. There is bound to be signifcant fragmentation
with the current design. The design was for rare allocations when
structures are initialized.

> Having a "properly scalable" percpu allocator would be quite nice indeed.

I guess we would be looking at a redesign of the allocator then.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/