From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Linux filesystem configuration infrastructure
Date: Sun, 3 Aug 2014 22:21:17 -0700 [thread overview]
Message-ID: <20140804052117.GA3517@kroah.com> (raw)
In-Reply-To: <CAMSEaH6MtHVX35i34a3jjNtxSYT=jQ0X+fJ-T5-AHd6xfWwO=Q@mail.gmail.com>
On Mon, Aug 04, 2014 at 10:20:35AM +0530, Sankar P wrote:
> Hi,
>
> I have a simple filesystem that I did for learning purpose
> https://github.com/psankar/simplefs
>
> Now, I would like to add a few settings to my filesystem (such as the
> number of blocks that should be allocated in an extent by default,
> maximum fragmentation score after which defrag should be automatically
> handled etc.) I would like to have the ability to not just set these
> settings, but export them to a file and restore these settings later.
> Is there some kind of a settings infrastructure code that is available
> in the linux kernel
configfs, but usually a filesystem doesn't need anything so complex,
just use the "normal" mount option way and you should be fine.
> I would also like to have some kind of validation system also as part
> of the settings interface. For example: If a setting can accept only
> ints, trying to set a string to that should be disabled, min and max
> values (range) for values of settings, etc.
Again, configfs is good for "complex" configurations.
Good luck,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Sankar P <sankar.curiosity@gmail.com>
Cc: kernelnewbies <Kernelnewbies@kernelnewbies.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: Linux filesystem configuration infrastructure
Date: Sun, 3 Aug 2014 22:21:17 -0700 [thread overview]
Message-ID: <20140804052117.GA3517@kroah.com> (raw)
In-Reply-To: <CAMSEaH6MtHVX35i34a3jjNtxSYT=jQ0X+fJ-T5-AHd6xfWwO=Q@mail.gmail.com>
On Mon, Aug 04, 2014 at 10:20:35AM +0530, Sankar P wrote:
> Hi,
>
> I have a simple filesystem that I did for learning purpose
> https://github.com/psankar/simplefs
>
> Now, I would like to add a few settings to my filesystem (such as the
> number of blocks that should be allocated in an extent by default,
> maximum fragmentation score after which defrag should be automatically
> handled etc.) I would like to have the ability to not just set these
> settings, but export them to a file and restore these settings later.
> Is there some kind of a settings infrastructure code that is available
> in the linux kernel
configfs, but usually a filesystem doesn't need anything so complex,
just use the "normal" mount option way and you should be fine.
> I would also like to have some kind of validation system also as part
> of the settings interface. For example: If a setting can accept only
> ints, trying to set a string to that should be disabled, min and max
> values (range) for values of settings, etc.
Again, configfs is good for "complex" configurations.
Good luck,
greg k-h
next prev parent reply other threads:[~2014-08-04 5:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 4:50 Linux filesystem configuration infrastructure Sankar P
2014-08-04 4:50 ` Sankar P
2014-08-04 5:21 ` Greg KH [this message]
2014-08-04 5:21 ` Greg KH
2014-08-04 15:00 ` Jan Kara
2014-08-04 15:00 ` Jan Kara
2014-08-04 15:15 ` Valdis.Kletnieks at vt.edu
2014-08-04 15:15 ` Valdis.Kletnieks
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=20140804052117.GA3517@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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.