The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: 김재극 <jaegeuk.kim@samsung.com>
Cc: viro@zeniv.linux.org.uk, "'Theodore Ts'o'" <tytso@mit.edu>,
	linux-kernel@vger.kernel.org, chur.lee@samsung.com,
	cm224.lee@samsung.com, jooyoung.hwang@samsung.com
Subject: Re: [PATCH 16/16] f2fs: update Kconfig and Makefile
Date: Fri, 5 Oct 2012 09:53:41 -0700	[thread overview]
Message-ID: <20121005165341.GB18344@kroah.com> (raw)
In-Reply-To: <001701cda2f1$ce1b3500$6a519f00$%kim@samsung.com>

On Fri, Oct 05, 2012 at 09:06:09PM +0900, 김재극 wrote:
> This adds Makefile and Kconfig for f2fs, and updates Makefile and Kconfig files
> in the fs directory.

I found it easier to comment about this here, instead of where the code
implemented this, as you describe it well here:

> +config F2FS_STAT_FS
> +	bool "F2FS Status Information"
> +	depends on F2FS_FS
> +	default y
> +	help
> +	  /proc/fs/f2fs/ contains information about partitions mounted as f2fs.
> +	  For each partition, a corresponding directory, named as its device
> +	  name, is provided with the following proc entries.
> +
> +	  f2fs_stat	major file system information managed by f2fs currently
> +	  f2fs_sit_stat	average SIT information about whole segments
> +	  f2fs_mem_stat	current memory footprint consumed by f2fs
> +
> +	  e.g., in /proc/fs/f2fs/sdb1/

As this is primarily debugging information, why not just always enable
it, and put in debugfs instead of in procfs?  That's where new debugging
information should be going.  Side benefit, your code should shrink a
bit if you use debugfs instead of procfs :)

Or, if this is really needed by all users, what is wrong with
/sys/fs/f2fs/ instead?

thanks,

greg k-h

  reply	other threads:[~2012-10-05 16:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-05 12:06 [PATCH 16/16] f2fs: update Kconfig and Makefile 김재극
2012-10-05 16:53 ` Greg KH [this message]
2012-10-06 17:58   ` Jaegeuk Kim

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=20121005165341.GB18344@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=chur.lee@samsung.com \
    --cc=cm224.lee@samsung.com \
    --cc=jaegeuk.kim@samsung.com \
    --cc=jooyoung.hwang@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    /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