public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Mingming Cao <cmm@us.ibm.com>
To: Badari Pulavarty <pbadari@gmail.com>
Cc: markn@au1.ibm.com, ext4 <linux-ext4@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Amit K. Arora" <aarora@linux.vnet.ibm.com>,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: [patch 1/2] add init_ext4_proc() stub for when CONFIG_PROC_FS is not set
Date: Tue, 09 Oct 2007 10:03:06 -0700	[thread overview]
Message-ID: <1191949386.3793.16.camel@localhost.localdomain> (raw)
In-Reply-To: <1191947487.12131.33.camel@dyn9047017100.beaverton.ibm.com>

On Tue, 2007-10-09 at 09:31 -0700, Badari Pulavarty wrote:
> On Tue, 2007-10-09 at 15:50 +1000, markn@au1.ibm.com wrote:
> > plain text document attachment (ext4-add-init_ext4_proc-stub.patch)
> > init_ext4_fs() calls init_ext4_proc() so we need a stub init_ext4_proc()
> > for the case that CONFIG_PROC_FS is not set.
> > Without the stub we get a build error:
> > 
> > fs/ext4/mballoc.c: In function 'init_ext4_proc':
> > fs/ext4/mballoc.c:2837: error: 'proc_root_fs' undeclared (first use in this function)
> > fs/ext4/mballoc.c:2837: error: (Each undeclared identifier is reported only once
> > fs/ext4/mballoc.c:2837: error: for each function it appears in.)
> > 
> > Add a stub init_ext4_proc() function that does nothing but return 0
> > 
> > Signed-off-by: Mark Nelson <markn@au1.ibm.com>
> > ---
> >  fs/ext4/mballoc.c |    7 +++++++
> >  1 file changed, 7 insertions(+)
> > 
> > Index: ext4/fs/ext4/mballoc.c
> > ===================================================================
> > --- ext4.orig/fs/ext4/mballoc.c
> > +++ ext4/fs/ext4/mballoc.c
> > @@ -2825,6 +2825,7 @@ static int ext4_mb_destroy_per_dev_proc(
> >  	return 0;
> >  }
> >  
> > +#ifdef CONFIG_PROC_FS
> >  int __init init_ext4_proc(void)
> >  {
> >  	ext4_pspace_cachep =
> > @@ -2840,6 +2841,12 @@ int __init init_ext4_proc(void)
> >  
> >  	return 0;
> >  }
> > +#else
> > +int __init init_ext4_proc(void)
> > +{
> > +	return 0;
> > +}
> > +#endif
> >  
> >  void exit_ext4_proc(void)
> >  {
> 
> Nope. I don't think we can do this :(
> 
> For example, we need to create ext4_pspace_cachep kmem cache 
> for the pre-allocation to work. We can't ifdef it out.
> 
> Mingming/Amit, can you take a look at this ? It looks like
> we NEED procfs support to make mballoc work. If so, we need
> to add it to the dependency.
> 
> 

I guess our testing did not catch this up because we have CONFIG_PROC_FS
enabled all the time. mballoc needs procfs for exporting some stats info
and tunable paramenters to optimize/customize multiple allocation.

We could select CONFIG_PROC_FS at kconfig when ext4dev is enabled.

Mingming

  reply	other threads:[~2007-10-09 17:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-09  5:50 [patch 0/2] ext4 fixups for 2.6.23-rc8-mm2/ext4 git tree markn
2007-10-09  5:50 ` [patch 1/2] add init_ext4_proc() stub for when CONFIG_PROC_FS is not set markn
2007-10-09 16:31   ` Badari Pulavarty
2007-10-09 17:03     ` Mingming Cao [this message]
2007-10-09 17:28       ` Badari Pulavarty
2007-10-09 17:40       ` Theodore Tso
2007-10-10  0:22         ` Theodore Tso
2007-10-10 15:30           ` Badari Pulavarty
2007-10-10 19:00             ` Theodore Tso
2007-10-11 20:00               ` Badari Pulavarty
2007-10-10  0:22     ` Mark Nelson
2007-10-09  5:50 ` [patch 2/2] move init_ext4_proc() last and add cleanup call exit_ext4_proc() markn
2007-10-09 16:22   ` Badari Pulavarty
2007-10-10  0:11     ` Mark Nelson
2007-10-10  0:34     ` Theodore Tso
2007-10-10  0:41   ` Theodore Tso
2007-10-10  0:50     ` Mark Nelson

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=1191949386.3793.16.camel@localhost.localdomain \
    --to=cmm@us.ibm.com \
    --cc=aarora@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=markn@au1.ibm.com \
    --cc=pbadari@gmail.com \
    /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