public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: revert "config FS_JOURNAL_INFO"
Date: Fri, 18 Dec 2009 16:48:02 +0900	[thread overview]
Message-ID: <4B2B33B2.9080900@ct.jp.nec.com> (raw)
In-Reply-To: <b6fcc0a0912172325i34d214d3r11b3bfae7381547f@mail.gmail.com>

Alexey Dobriyan wrote:
> On 12/18/09, Hiroshi Shimamoto <h-shimamoto@ct.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

  reply	other threads:[~2009-12-18  7:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-17  8:31 revert "config FS_JOURNAL_INFO" Alexey Dobriyan
2009-12-17 20:09 ` Andrew Morton
2009-12-18  4:04 ` Hiroshi Shimamoto
2009-12-18  7:25   ` Alexey Dobriyan
2009-12-18  7:48     ` Hiroshi Shimamoto [this message]
2009-12-19 11:51     ` OGAWA Hirofumi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B2B33B2.9080900@ct.jp.nec.com \
    --to=h-shimamoto@ct.jp.nec.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox