linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: hooanon05@yahoo.co.jp
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC Aufs2 #3 2/2] split 'xino' entry under sysfs
Date: Fri, 20 Mar 2009 11:25:49 +0900	[thread overview]
Message-ID: <3934.1237515949@jrobl> (raw)
In-Reply-To: <20090320004539.GF18781@kroah.com>


Greg KH:
> > +Description:
> > +		It shows the consumed blocks by xib (External Inode Number
> > +		Bitmap), its block size and file size.
> > +		When the aufs mount option 'noxino' is specified, it
> > +		will be empty. About XINO files, see
> > +		Documentation/filesystems/aufs/aufs.5 in detail.
> 
> Sysfs files are one value per file.  This violates that rule.

Current print format is 
	"%llux%lu %lld\n", st->blocks, st->blksize, (long long)st->size

Do you mean this has three values and violates the rule?
And aufs should create three entries such like xib/blocks, xib/blksize
and xib/size?
If I change it "<blocks>x<blksize>", is it still violation?


> Are all of these things something that a "normal" user would care about?
> or are they development / debugging things?

Normal users want to care them, I guess.
Since XINO files grow only, some heavy users had met ENOSPC
actually. Currently aufs supports automatic truncation for XINO files in
tmpfs only.


> And why are you using seq_file for a sysfs file?  That's not allowed,
> and a sure sign you are doing something wrong, please remove all of
> that.

I just wanted to set limit its size to PAGE_SIZE to print the absolute
path. Is there another better approach?


Thank you for reviewing
J. R. Okajima

  reply	other threads:[~2009-03-20  2:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-19  5:12 [RFC Aufs2 #3 0/2] 'debug' module parm and /sys/fs/aufs entries J. R. Okajima
2009-03-19  5:12 ` [RFC Aufs2 #3 1/2] replace /sys/fs/aufs/debug by /sys/module/aufs/parmaters/debug J. R. Okajima
2009-03-19  5:12 ` [RFC Aufs2 #3 2/2] split 'xino' entry under sysfs J. R. Okajima
2009-03-20  0:45   ` Greg KH
2009-03-20  2:25     ` hooanon05 [this message]
2009-03-20  2:42       ` Greg KH
2009-03-20  2:55         ` hooanon05
2009-03-20  3:06           ` Greg KH
2009-03-20  3:59             ` hooanon05
2009-03-20  4:18               ` Greg KH
2009-03-20  5:15                 ` hooanon05
2009-03-20  5:44                   ` Greg KH
2009-03-24  8:16                     ` Q. DEBUG_FS and SYSFS config (Re: [RFC Aufs2 #3 2/2] split 'xino' entry under sysfs) hooanon05
2009-03-24 15:33                       ` Greg KH
2009-03-24 15:57                         ` Kay Sievers
2009-03-24 23:20                           ` Greg KH

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=3934.1237515949@jrobl \
    --to=hooanon05@yahoo.co.jp \
    --cc=greg@kroah.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).