From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTP id 891044D4 for ; Thu, 15 May 2014 19:42:35 +0000 (UTC) Received: from mail.zytor.com (terminus.zytor.com [198.137.202.10]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 524F0200A7 for ; Thu, 15 May 2014 19:42:35 +0000 (UTC) Message-ID: <53751887.1040809@zytor.com> Date: Thu, 15 May 2014 12:41:59 -0700 From: "H. Peter Anvin" MIME-Version: 1.0 To: Li Zefan , James Bottomley References: <1399595490.2230.13.camel@dabdike.int.hansenpartnership.com> <5372D6E4.2080009@huawei.com> In-Reply-To: <5372D6E4.2080009@huawei.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Sarah Sharp , ksummit-discuss@lists.linuxfoundation.org, Greg KH , Julia Lawall , Darren Hart , Dan Carpenter Subject: Re: [Ksummit-discuss] [CORE TOPIC] Kernel tinification: shrinking the kernel and avoiding size regressions List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 05/13/2014 07:37 PM, Li Zefan wrote: > > Mel has recently working on a patchset for mm optimization, and I > just noticed one particular patch adds static_key to eliminate cpuset > overhead in mm code path. We sure can use static_key more in cgroup. > > New features tend to add new stuff to structures like task_struct, which > static_key or any other mechanisms can't help. > Not to mention that static_key does nothing in a ROM-size-limited application. I think kernel tinification and what should be acceptable goals and non-goals for the mainline kernel would make an excellent KS topic. Personally, I am for stretching Linux as far across the compute spectrum as it can possibly go. -hpa