From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>,
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: Sat, 19 Dec 2009 20:51:49 +0900 [thread overview]
Message-ID: <877hsjw59m.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <b6fcc0a0912172325i34d214d3r11b3bfae7381547f@mail.gmail.com> (Alexey Dobriyan's message of "Fri, 18 Dec 2009 09:25:51 +0200")
Alexey Dobriyan <adobriyan@gmail.com> writes:
> 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.
>
>> 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.
Why doesn't this use EMBEDDED?
I.e.
boot "xxx" if EMBEDDED
default y
style Kconfig.
Only reason which seems reasonable is "this is done only for one pointer
on task_struct". This reason seems something like "You care, but I don't
care it". And, other reasons is *normal* situation on EMBEDDED, right?
Thanks.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
prev parent reply other threads:[~2009-12-19 11:51 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
2009-12-19 11:51 ` OGAWA Hirofumi [this message]
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=877hsjw59m.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=h-shimamoto@ct.jp.nec.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.