Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752453AbZLRHZz (ORCPT ); Fri, 18 Dec 2009 02:25:55 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751521AbZLRHZy (ORCPT ); Fri, 18 Dec 2009 02:25:54 -0500 Received: from mail-bw0-f227.google.com ([209.85.218.227]:56477 "EHLO mail-bw0-f227.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751440AbZLRHZx (ORCPT ); Fri, 18 Dec 2009 02:25:53 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=kiYi7ZwfXNAuLNhm10aqazryOiyzaqq+5VCmtjP0ARy4IjWueqdtJ1k3mXqmtMbSAX bhijRrFkczWphInBpAtHSXD+BtloS9f/ITM8JI0XpHFonq+dXsppGkO7EuaLFjZkq0nk l0cEqzRiMe7ZEXEKpg+nR9oMKgU6IrS9WiG7o= MIME-Version: 1.0 In-Reply-To: <4B2AFF4C.5010100@ct.jp.nec.com> References: <4B2AFF4C.5010100@ct.jp.nec.com> Date: Fri, 18 Dec 2009 09:25:51 +0200 Message-ID: Subject: Re: revert "config FS_JOURNAL_INFO" From: Alexey Dobriyan To: Hiroshi Shimamoto Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org, linux-fsdevel , linux-kernel@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 778 Lines: 17 On 12/18/09, Hiroshi Shimamoto wrote: > So we never allow to make memory usage small with providing an option > to remove unused area, right? We certainly allow this if it results in zero loss in functionality. > If I want to reduce memory usage by this way, should I keep > this kind of patches out of tree? Certainly nobody can prohibit you from keeping patch out of tree. But if you want something mainlinable, moving ->journal_info to fs-specific data structures should do the trick. Or something. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/