public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
To: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
	linux-kernel@vger.kernel.org, mm-commits@vger.kernel.org,
	chris.mason@oracle.com, swhiteho@redhat.com, tytso@mit.edu
Subject: Re: + task_struct-make-journal_info-conditional.patch added to -mm tree
Date: Tue, 08 Dec 2009 09:32:47 +0900	[thread overview]
Message-ID: <4B1D9EAF.90906@ct.jp.nec.com> (raw)
In-Reply-To: <200912070929.AA01196@capsicum.lab.ntt.co.jp>

Ryusuke Konishi wrote:
>> Alexey Dobriyan wrote:
>>> On Fri, Dec 04, 2009 at 12:58:06PM +0900, Hiroshi Shimamoto wrote:
>>>> Alexey Dobriyan wrote:
>>>>> On Thu, Dec 03, 2009 at 02:40:57PM -0800, akpm@linux-foundation.org wrote:
>>>>>> --- a/include/linux/sched.h~task_struct-make-journal_info-conditional
>>>>>> +++ a/include/linux/sched.h
>>>>>> @@ -1452,8 +1452,10 @@ struct task_struct {
>>>>>>  	gfp_t lockdep_reclaim_gfp;
>>>>>>  #endif
>>>>>>  
>>>>>> +#ifdef CONFIG_FS_JOURNAL_INFO
>>>>>>  /* journalling filesystem info */
>>>>>>  	void *journal_info;
>>>>>> +#endif
>>>>> This will prevent using e.g. ext3 on CONFIG_EXT3_FS=n kernels.
>>>> I'm sorry, I'm not sure what you're mentioning.
>>> With this patch admin must decide in advance if he will ever use ext3.
>>> EXT3_FS=n kernels won't be able to get ext3 support without reboot
>>> even as module, because task_struct will be different.
>> I see, you want to keep this field for future use even if EXT3_FS=n.
>> I think, however, there might be a need to remove this because the user
>> never enable any journaling filesystem.
> 
> Do you have some background to remove the "void *" from task_struct?
> You need it for embedded purpose?

Yeah, it's for embedded. I think it's good if there is a option to make
memory usage small.

Thanks,
Hiroshi


      reply	other threads:[~2009-12-08  0:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200912032240.nB3Mevae027408@imap1.linux-foundation.org>
2009-12-04  2:14 ` + task_struct-make-journal_info-conditional.patch added to -mm tree Alexey Dobriyan
2009-12-04  3:58   ` Hiroshi Shimamoto
2009-12-04  5:17     ` Alexey Dobriyan
2009-12-04  9:31       ` Steven Whitehouse
2009-12-07  2:28       ` Hiroshi Shimamoto
2009-12-07  4:30         ` Alexey Dobriyan
2009-12-07  9:29         ` Ryusuke Konishi
2009-12-08  0:32           ` Hiroshi Shimamoto [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=4B1D9EAF.90906@ct.jp.nec.com \
    --to=h-shimamoto@ct.jp.nec.com \
    --cc=adobriyan@gmail.com \
    --cc=chris.mason@oracle.com \
    --cc=konishi.ryusuke@lab.ntt.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=swhiteho@redhat.com \
    --cc=tytso@mit.edu \
    /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