linux-kernel - Re: More problems in setup_pcpu

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]

Date:	Wed, 01 Apr 2009 21:52:33 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	tj@...nel.org
Cc:	linux-kernel@...r.kernel.org
Subject: Re: More problems in setup_pcpu_remap()

From: Tejun Heo <tj@...nel.org>
Date: Thu, 02 Apr 2009 13:42:57 +0900

> I guess we'll have to put a cap on how high possible cpus can be for
> remap allocator.  e.g. if single chunk size is over 20% of the whole
> vmalloc area, don't use remap.  Does anyone have a good random %
> number on mind?

I would suggest instead to rethink what this code is doing.

It would make more sense to carve up 2MB chunks into some-power-of-2
pieces and use that as the unit size.

You could retain the NUMA goals of this function, as well as the
ability to be using 2MB pages in the TLBs.

And consider that if the dynamic allocation part of this code triggers
even once, you'll end up eating twice as much VMALLOC space.

Using 2MB per cpu is just rediculious, and really not even necessary.
--
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/