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-next>] [day] [month] [year] [list]
Message-ID: <20110226143730.GA26864@htj.dyndns.org>
Date:	Sat, 26 Feb 2011 15:37:30 +0100
From:	Tejun Heo <tj@...nel.org>
To:	Ingo Molnar <mingo@...hat.com>, "H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Yinghai Lu <yinghai@...nel.org>
Cc:	linux-kernel@...r.kernel.org
Subject: [RFC] Reverting NUMA-affine page table allocation

Hello,

I've been looking through NUMA-affine page table allocation code and
the proposed changes, and there currently are the a couple of
problems.

1. Holes or misaligned nodes will force use of smaller sized mappings.
   Patches to fix the problem have been posted by Yinghai[1].

2. find_early_table_space() always calculates the amount of the needed
   space from 0 to the specified @end.  As nodes are registered, each
   node would try to allocate accumulative amount of space for page
   table.  This probably wouldn't cause any actual problem (may affect
   emulated configurations a bit tho).

IMHO, it would be better to avoid adding fixes for #1 and #2 at this
stage as we're very close to the next merge window and this is
(somewhat unnecessarily) delicate piece of code.  Also, I do think
that the NUMA affine page table allocation is generally overdone given
its limited usefulness when 1GiB mapping is available.

I'd like to revert NUMA-affine page table allocation for now and come
back to it in the next devel cycle.  Thanks to the memblock top-down
change, the RED-PEN condition (page table ending up in DMA memory)
doesn't exist with or without NUMA affine allocation and the only
downside of reverting would be page tables allocated in foreign nodes
on machines which don't support 1GiB mapping.

What do you think?

Thanks.

-- 
tejun

[1] http://thread.gmane.org/gmane.linux.kernel/1104672
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ