From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id C17B0138CD0 for ; Fri, 22 May 2015 22:20:12 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BDC3BE097E; Fri, 22 May 2015 22:20:04 +0000 (UTC) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 9015BE0976 for ; Fri, 22 May 2015 22:20:03 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1YvvIP-0006Qw-4r for gentoo-user@lists.gentoo.org; Sat, 23 May 2015 00:20:01 +0200 Received: from 64.69.39.112 ([64.69.39.112]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 23 May 2015 00:20:01 +0200 Received: from w41ter by 64.69.39.112 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 23 May 2015 00:20:01 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: walt Subject: [gentoo-user] Re: [~and64] Headsup for google-chrome users Date: Fri, 22 May 2015 15:19:56 -0700 Message-ID: References: <555E6F22.8090200@gmail.com> <201505221433.01581.michaelkintzios@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 64.69.39.112 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 In-Reply-To: X-Archives-Salt: cb1a95ab-afdd-4b26-949a-f6ce42aca794 X-Archives-Hash: b7b5df544f7a98fe30ea3a7d456b8f17 On 05/22/2015 02:38 PM, Tom H wrote: > On Fri, May 22, 2015 at 5:13 PM, walt wrote: >> On 05/22/2015 06:32 AM, Mick wrote: >>> >>> Did you also enable CONFIG_MEMCG & MEMCG_KMEM in your kernel? >> >> When I use the search function in "make menuconfig" I don't see any mention >> of MEMCG, so I suspect that particular config item must be enabled by some >> other config option that I didn't enable (though I don't remember making >> that decision one way or the other). >> >> I'm running gentoo-sources-3.14.42. > > You must've mistype your search: > > $ grep MEMCG init/Kconfig > config MEMCG > config MEMCG_SWAP > depends on MEMCG && SWAP > config MEMCG_SWAP_ENABLED > depends on MEMCG_SWAP > config MEMCG_KMEM > depends on MEMCG > recommended that the MEMCG and MEMCG_KMEM options also be > > The above was from 4.1.0-rc4 but AFAIK it's existed for 2 or 3 years > so you should have it in 3.14. Yes, I agree that MEMCG has been in the kernel source code for years. I want to emphasize (for any future googlers) that the selection (or de-selection) of kernel config options can change what you can find or can't find when configuring kernel options in "make menuconfig". This is important, and I want to drill this concept home in your (collective) brains. Configuring the linux kernel is *not* simple. The kernel devs have been struggling with this idea for years, and I am certainly no smarter than they are. Please, just understand that the kernel config scripts are fallible, just like the people who write them.