| 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
| ||
|
Message-ID: <alpine.LFD.2.01.0905311613260.3435@localhost.localdomain> Date: Sun, 31 May 2009 16:15:50 -0700 (PDT) From: Linus Torvalds <torvalds@...ux-foundation.org> To: Andrew Morton <akpm@...ux-foundation.org> cc: Alexey Dobriyan <adobriyan@...il.com>, Matt Helsley <matthltc@...ibm.com>, xemul@...allels.com, containers@...ts.linux-foundation.org, linux-kernel@...r.kernel.org, dave@...ux.vnet.ibm.com, mingo@...e.hu Subject: Re: [PATCH 14/38] Remove struct mm_struct::exe_file et al On Sun, 31 May 2009, Andrew Morton wrote: > > What I always find a bit weird is that an MM container is used as the > central point for a number of sched obects. But it's logical, given > that the never-before-stated definition of a heavyweight process is > "thing which share a VM". It has nothing to do with "heavy-weight process" or anything else. The thing is, from a scheduling standpoint, one of the primary performance concerns in the TLB switch. And there's a 1:1 relationship between TLB switch and MM container, modulo the issue of kernel tasks (and those obviously "borrow" approproate MM structs to avoid the switch). So it's not weird at all. It's very direct, and a very straightforward and obvious relationship. Linus -- 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