linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: "Luis R. Rodriguez" <mcgrof@kernel.org>,
	linux-xfs@vger.kernel.org, jack@suse.com, jeffm@suse.com,
	okurz@suse.com, lpechacek@suse.com, jtulak@redhat.com,
	tytso@mit.edu
Subject: Re: [PATCH] mkfs.xfs: add configuration file parsing support using our own parser
Date: Fri, 4 May 2018 14:36:46 -0700	[thread overview]
Message-ID: <20180504213646.GO26569@magnolia> (raw)
In-Reply-To: <54b16a43-353a-6cde-34ce-04d678131b0c@sandeen.net>

On Fri, May 04, 2018 at 04:31:56PM -0500, Eric Sandeen wrote:
> On 3/13/18 10:21 PM, Eric Sandeen wrote:
> >> There is only a subset of options allowed to be set on the configuration
> >> file, 
> 
> > I think this is problematic - allowing only booleans is pretty
> > arbitrary.
> 
> ...
>  
> >> and currently only 1 or 0 are acceptable values. The default
> >> parameters you can override on a configuration file and their current
> >> built-in default settings are:
> >>
> >> [data]
> >> noalign=0
> 
> ...
> 
> >> We have floated around enough bike shedding emails to have at least reached
> >> a consensus on the fact that we'd be only supporting a mimimum set of default
> >> parameters and would strive to simplify our parser as much as possible.
> 
> > See above - sorry for not chiming in sooner, but I don't think an arbitrary
> > restriction to the boolean options will be sufficient in the long run.
> 
> Ok, I'm rethinking this concern now.
> 
> It seems like we may have two separate but related purposes for a mkfs config file:
> 
> 1) Set system-wide defaults based on kernel and/or OS support.
> 2) Set specific-use defaults, such as "mkfs.xfs -c gluster" etc.
> 
> For the former, it may well only be the booleans that matter.  For the latter,
> it may be more, like setting inode size, or directory block size, etc.
> 
> Is there anything we'd reasonably want to set system-wide that's /not/ a
> boolean?  If not, the maybe that can be Phase 1 as long as the config file
> format doesn't need to change; we can just add to the list of supported config
> options at a later date, perhaps?

Looking at the *documented* mkfs options, I think it'd be useful for
cloud users to be able to set cowextsize and extsize from mkfs.

As I was saying on irc, I /think/ the options (Allison feel free to
chime in here) that we want are....

-m crc,finobt,rmapbt,reflink,projinherit,extszinherit,cowextsize,extsize
-i maxpct,sparse
-n ftype

--D

> The system-wide, supported-features default config may be the most pressing
> need at this point, the rest is just nice to have.
> 
> Thanks,
> -Eric
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2018-05-04 21:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-13 20:59 [PATCH] mkfs.xfs: add configuration file parsing support using our own parser Luis R. Rodriguez
2018-03-13 21:39 ` Dave Chinner
2018-03-13 23:52   ` Luis R. Rodriguez
2018-03-14  3:55     ` Dave Chinner
2018-03-14 17:19       ` Luis R. Rodriguez
2018-03-14 21:01         ` Dave Chinner
2018-03-14 22:13           ` Luis R. Rodriguez
2018-04-26 17:37           ` Luis R. Rodriguez
2018-05-03  0:00             ` Luis R. Rodriguez
2018-05-11 22:20               ` Luis R. Rodriguez
2018-03-14  3:21 ` Eric Sandeen
2018-03-14 18:41   ` Luis R. Rodriguez
2018-05-04 21:31   ` Eric Sandeen
2018-05-04 21:36     ` Darrick J. Wong [this message]
2018-05-04 21:39       ` Eric Sandeen
2018-05-17 18:47       ` Luis R. Rodriguez

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=20180504213646.GO26569@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=jack@suse.com \
    --cc=jeffm@suse.com \
    --cc=jtulak@redhat.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=lpechacek@suse.com \
    --cc=mcgrof@kernel.org \
    --cc=okurz@suse.com \
    --cc=sandeen@sandeen.net \
    --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;
as well as URLs for NNTP newsgroup(s).