From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Jan Tulak <jtulak@redhat.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 6/6] mkfs: extend opt_params with a value field
Date: Mon, 14 Aug 2017 16:15:53 -0700 [thread overview]
Message-ID: <20170814231553.GJ4796@magnolia> (raw)
In-Reply-To: <20170811123037.15962-7-jtulak@redhat.com>
On Fri, Aug 11, 2017 at 02:30:37PM +0200, Jan Tulak wrote:
> This patch adds infrastructure that will be used in subsequent patches.
>
> The Value field is the actual value used in computations for creating
> the filesystem. This is initialized with sensible default values. If
> initialized to 0, the value is considered disabled. User input will
> override default values. If the field is a string and not a number, the
> value is set to a positive non-zero number when user input has been
> supplied.
>
> Add functions that can be used to get/set values to opts table.
>
> Signed-off-by: Jan Tulak <jtulak@redhat.com>
>
> ---
> Change:
> * make the value type to be long long instead of uint64 for now
> * add collateral updates
> * add bounds to get/set functions
> * update the description of commit/in code
> * merge with another patch, which adds the get/set functions.
> ---
> mkfs/xfs_mkfs.c | 194 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 194 insertions(+)
>
> diff --git a/mkfs/xfs_mkfs.c b/mkfs/xfs_mkfs.c
> index 3e7ba5f0..61ef09e8 100644
> --- a/mkfs/xfs_mkfs.c
> +++ b/mkfs/xfs_mkfs.c
> @@ -117,6 +117,13 @@ unsigned int sectorsize;
> * Filled raw string from the user, so we never lose that information e.g.
> * to print it back in case of an issue.
> *
> + * value OPTIONAL
> + * The actual value used in computations for creating the filesystem.
> + * This is initialized with sensible default values. If initialized to 0,
> + * the value is considered disabled. User input will override default
> + * values. If the field is a string and not a number, the value is set to
> + * a positive non-zero number when user input has been supplied.
> + *
> */
> struct opt_params {
> int index;
> @@ -134,6 +141,7 @@ struct opt_params {
> long long maxval;
> long long flagval;
> char *raw_input;
> + long long value;
I think this is less sensitive for mkfs options, but for structures
please keep variables of the same type together to reduce memory usage.
That (char *) between the (long long) creates a 4-byte padding hole on
32-bit machines. I recommend pahole for things like this.
> } subopt_params[MAX_SUBOPTS];
> } opts[MAX_OPTS] = {
> #define OPT_B 0
> @@ -750,6 +758,180 @@ struct opt_params {
> #define WHACK_SIZE (128 * 1024)
>
> /*
> + * Get and set values to the opts table.
> + */
> +static int
> +get_conf_val_unsafe(int opt, int subopt, uint64_t *output)
> +{
> + if (subopt < 0 || subopt >= MAX_SUBOPTS ||
> + opt < 0 || opt >= MAX_OPTS) {
> + fprintf(stderr,
> + "This is a bug: get_conf_val called with invalid opt/subopt: %d/%d\n",
Oh yeah, I forgot to mention this a few patches back -- if these remain
fprintfs, then shouldn't the string be enclosed in _() so that strings
can be localized?
> + opt, subopt);
> + return -EINVAL;
> + }
> + *output = opts[opt].subopt_params[subopt].value;
> + return 0;
> +}
> +
> +static long long
> +get_conf_val(int opt, int subopt)
> +{
> + uint64_t res;
> + if (get_conf_val_unsafe(opt, subopt, &res) != 0)
> + exit(1);
Tab then space indentation problem here.
> + return res;
> +}
> +
> +static int
> +set_conf_val_unsafe(int opt, int subopt, uint64_t val)
> +{
> + if (subopt < 0 || subopt >= MAX_SUBOPTS ||
> + opt < 0 || opt >= MAX_OPTS) {
> + fprintf(stderr,
> + "This is a bug: set_conf_val called with invalid opt/subopt: %d/%d\n",
> + opt, subopt);
> + return -EINVAL;
> + }
> + struct subopt_param *sp = &opts[opt].subopt_params[subopt];
> + sp->value = val;
> +
> + return 0;
> +}
> +
> +static void
> +set_conf_val(int opt, int subopt, uint64_t val)
> +{
> + if (set_conf_val_unsafe(opt, subopt, val) != 0)
> + exit(1);
> +}
> +
> +/*
> + * A wrapper around set_conf_val which updates also connected/collateral values.
> + * E.g. when changing S_LOG, update S_SIZE too.
> + */
> +static void
> +set_conf_val_collateral(int opt, int subopt, uint64_t val)
"collateral"... I hope we're not trying to secure a loan here. :)
I suggest using "connected" (or "correlated") here instead.
> +{
> + set_conf_val(opt, subopt, val);
> +
> + switch (opt) {
> + case OPT_B:
> + switch (subopt) {
> + case B_LOG:
> + set_conf_val(OPT_B, B_SIZE, 1 << val);
> + break;
> + case B_SIZE:
> + set_conf_val(OPT_B, B_LOG,
> + libxfs_highbit32(val));
> + break;
> + }
> + break;
> + case OPT_D:
> + switch (subopt) {
> + case D_SECTLOG:
> + set_conf_val(OPT_S, S_LOG, val);
> + set_conf_val(OPT_S, S_SECTLOG, val);
> + set_conf_val(OPT_D, D_SECTSIZE,
> + 1 << val);
> + set_conf_val(OPT_S, S_SECTSIZE,
> + 1 << val);
> + set_conf_val(OPT_S, S_SIZE,
> + 1 << val);
> + break;
> + case D_SECTSIZE:
> + set_conf_val(OPT_S, S_SIZE, val);
> + set_conf_val(OPT_S, S_SECTSIZE, val);
> + set_conf_val(OPT_D, D_SECTLOG,
> + libxfs_highbit32(val));
> + set_conf_val(OPT_S, S_LOG,
> + libxfs_highbit32(val));
> + set_conf_val(OPT_S, S_SECTLOG,
> + libxfs_highbit32(val));
> + break;
> + }
> + break;
> + case OPT_I:
> + switch (subopt) {
> + case I_LOG:
> + set_conf_val(OPT_I, I_SIZE, 1 << val);
> + break;
> + case I_SIZE:
> + set_conf_val(OPT_I, I_LOG,
> + libxfs_highbit32(val));
> + break;
> + }
> + break;
> + case OPT_L:
> + switch (subopt) {
> + case L_SECTLOG:
> + set_conf_val(OPT_L, L_SECTSIZE,
> + 1 << val);
> + break;
> + case L_SECTSIZE:
> + set_conf_val(OPT_L, L_SECTLOG,
> + libxfs_highbit32(val));
Tab/space indentation problem here too.
(Wondering if the calls here are short enough for a single line?)
> + break;
> + }
> + break;
> + case OPT_M:
> + switch (subopt) {
> + }
> + break;
> + case OPT_N:
> + switch (subopt) {
> + case N_LOG:
> + set_conf_val(OPT_N, N_SIZE, 1 << val);
> + break;
> + case N_SIZE:
> + set_conf_val(OPT_N, N_LOG,
> + libxfs_highbit32(val));
> + break;
> + }
> + break;
> + case OPT_R:
> + switch (subopt) {
> + }
> + break;
> + case OPT_S:
> + switch (subopt) {
> + case S_LOG:
> + case S_SECTLOG:
> + set_conf_val(OPT_S, S_LOG, val);
> + set_conf_val(OPT_D, D_SECTLOG, val);
> + set_conf_val(OPT_L, L_SECTLOG, val);
> + set_conf_val(OPT_D, D_SECTSIZE,
> + 1 << val);
> + set_conf_val(OPT_S, S_SIZE, 1 << val);
> + set_conf_val(OPT_S, S_SECTSIZE,
> + 1 << val);
> + set_conf_val(OPT_L, L_SECTLOG, val);
> + set_conf_val(OPT_L,
> + L_SECTSIZE, 1 << val);
> +
> + set_conf_val(OPT_L, L_SECTSIZE, val);
> + break;
> + case S_SIZE:
> + case S_SECTSIZE:
> + set_conf_val(OPT_S, S_SIZE, val);
> + set_conf_val(OPT_D, D_SECTSIZE, val);
> + set_conf_val(OPT_D, D_SECTLOG,
> + libxfs_highbit32(val));
> + set_conf_val(OPT_S, S_LOG,
> + libxfs_highbit32(val));
> + set_conf_val(OPT_S, S_SECTLOG,
> + libxfs_highbit32(val));
> + set_conf_val(OPT_L,
> + L_SECTSIZE, val);
> + set_conf_val(OPT_L, L_SECTLOG,
> + libxfs_highbit32(val));
> + break;
> + }
> + break;
> + }
> +}
> +
> +/*
> * Return 0 on success, -ENOMEM if it could not allocate enough memory for
> * the string to be saved.
> */
> @@ -932,6 +1114,18 @@ getnum(
> }
>
> /*
> + * A wrapper for getnum and set_conf_val.
> + */
> +static inline long long
> +parse_conf_val(int opt, int subopt, char *value)
> +{
> + long long num = getnum(value, &opts[opt], subopt);
> +
> + set_conf_val_collateral(opt, subopt, num);
> + return num;
> +}
> +
> +/*
> * Convert lsu to lsunit for 512 bytes blocks and check validity of the values.
> */
> static void
> --
> 2.13.3
>
> --
> 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
next prev parent reply other threads:[~2017-08-14 23:15 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 12:30 [PATCH 0/6 v2] mkfs: save user input into opts table Jan Tulak
2017-08-11 12:30 ` [PATCH 1/6] mkfs: Save raw user input field to the opts struct Jan Tulak
2017-08-14 22:56 ` Darrick J. Wong
2017-08-15 9:47 ` Jan Tulak
2017-08-11 12:30 ` [PATCH 2/6] mkfs: rename defaultval to flagval in opts Jan Tulak
2017-08-14 22:56 ` Darrick J. Wong
2017-08-11 12:30 ` [PATCH 3/6] mkfs: remove intermediate getstr followed by getnum Jan Tulak
2017-08-14 22:58 ` Darrick J. Wong
2017-08-11 12:30 ` [PATCH 4/6] mkfs: merge tables for opts parsing into one table Jan Tulak
2017-08-14 23:06 ` Darrick J. Wong
2017-08-15 10:05 ` Jan Tulak
2017-08-11 12:30 ` [PATCH 5/6] mkfs: move getnum within the file Jan Tulak
2017-08-14 23:07 ` Darrick J. Wong
2017-08-15 10:14 ` Jan Tulak
2017-08-15 21:09 ` Eric Sandeen
2017-08-16 9:25 ` Jan Tulak
2017-08-11 12:30 ` [PATCH 6/6] mkfs: extend opt_params with a value field Jan Tulak
2017-08-14 23:15 ` Darrick J. Wong [this message]
2017-08-15 10:42 ` Jan Tulak
2017-08-15 15:08 ` [PATCH 1/6 v2] mkfs: Save raw user input field to the opts struct Jan Tulak
2017-08-15 15:08 ` [PATCH 3/6 v2] mkfs: remove intermediate getstr followed by getnum Jan Tulak
2017-08-15 23:20 ` Eric Sandeen
2017-08-17 11:36 ` Dave Chinner
2017-08-15 15:08 ` [PATCH 4/6 v2] mkfs: merge tables for opts parsing into one table Jan Tulak
2017-08-15 15:08 ` [PATCH 5/6 v2] mkfs: move getnum within the file Jan Tulak
2017-08-15 15:08 ` [PATCH 6/6 v2] mkfs: extend opt_params with a value field Jan Tulak
2017-08-16 21:13 ` Eric Sandeen
2017-08-16 21:38 ` Darrick J. Wong
2017-08-17 10:08 ` Jan Tulak
2017-08-17 11:03 ` Dave Chinner
2017-08-17 14:56 ` Jan Tulak
2017-08-17 22:59 ` Dave Chinner
2017-08-17 15:26 ` Eric Sandeen
2017-08-15 23:07 ` [PATCH 1/6 v2] mkfs: Save raw user input field to the opts struct Eric Sandeen
2017-08-16 9:11 ` Jan Tulak
2017-08-16 14:42 ` Eric Sandeen
2017-08-16 15:38 ` Jan Tulak
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=20170814231553.GJ4796@magnolia \
--to=darrick.wong@oracle.com \
--cc=jtulak@redhat.com \
--cc=linux-xfs@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