[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B2B33B2.9080900@ct.jp.nec.com>
Date: Fri, 18 Dec 2009 16:48:02 +0900
From: Hiroshi Shimamoto <h-shimamoto@...jp.nec.com>
To: Alexey Dobriyan <adobriyan@...il.com>
CC: torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
linux-kernel@...r.kernel.org
Subject: Re: revert "config FS_JOURNAL_INFO"
Alexey Dobriyan wrote:
> On 12/18/09, Hiroshi Shimamoto <h-shimamoto@...jp.nec.com> 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.
Thanks for clarifying this topic.
If you don't mind could you please tell me what zero loss is?
I don't think I could get it exactly.
Is it OK that removing journal_info if !CONFIG_BLOCK?
>
>> 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.
Thanks for the advice, I'll look at this.
Thanks,
Hiroshi
--
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