public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Brian Foster <bfoster@redhat.com>
Cc: dchinner@redhat.com, xfs@oss.sgi.com
Subject: Re: [PATCH RFC] xfs_spaceman: updated preallocation support (eofblocks v6)
Date: Wed, 7 Nov 2012 09:43:37 +1100	[thread overview]
Message-ID: <20121106224337.GL24575@dastard> (raw)
In-Reply-To: <1352213704-59959-1-git-send-email-bfoster@redhat.com>

On Tue, Nov 06, 2012 at 09:55:04AM -0500, Brian Foster wrote:
> This is an update to Dave's patch to xfs_spaceman to support
> preallocation trimming. The original patch is here:
> 
> http://oss.sgi.com/archives/xfs/2012-10/msg00418.html
> 
> The code is updated as follows:
> 
> - Update to latest struct xfs_eofblocks (supports v6 of the
>   speculative preallocation inode tracking set).
> - Support multiple id scan.
> - Fix the minimum argument count (no args means a trylock scan).
> 
> Signed-off-by: Brian Foster <bfoster@redhat.com>
> ---
> 
> Dave,
> 
> I can also squash this into the original and post a new version if that is
> preferred. 

I'll probably do that myself - the current code I have is a little
different so the patch probably won't apply, anyway.  I'll need to
munge it to suit the eventual struct xfs_eofblocks format, anyway.

....

> @@ -136,7 +142,7 @@ prealloc_help(void)
>  "\n"
>  "Control speculative preallocation\n"
>  "\n"
> -"Options: [-s] [-ugp id] [-m minlen]\n"
> +"Options: [-s] [-u id] [-g id] [-p id] [-m minlen]\n"
>  "\n"
>  " -s -- synchronous flush - wait for flush to complete\n"
>  " -u id -- remove prealloc on files matching user quota id <id>\n"
> @@ -153,11 +159,11 @@ prealloc_init(void)
>  	prealloc_cmd.name = "prealloc";
>  	prealloc_cmd.altname = "prealloc";
>  	prealloc_cmd.cfunc = prealloc_f;
> -	prealloc_cmd.argmin = 1;
> +	prealloc_cmd.argmin = 0;

While technically correct, it's not the desired behaviour.  I wanted
it to issue the usage if you just type the comment. I think I need
to add a "-a" flag for "flush all" here.

> -	prealloc_cmd.oneline = _("Control specualtive preallocation");
> +	prealloc_cmd.oneline = _("Control speculative preallocation");

Good catch, Brain! :)

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2012-11-06 22:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-06 14:55 [PATCH RFC] xfs_spaceman: updated preallocation support (eofblocks v6) Brian Foster
2012-11-06 22:43 ` Dave Chinner [this message]
2012-11-06 22:58   ` Brian Foster

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=20121106224337.GL24575@dastard \
    --to=david@fromorbit.com \
    --cc=bfoster@redhat.com \
    --cc=dchinner@redhat.com \
    --cc=xfs@oss.sgi.com \
    /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