From: Brian Foster <bfoster@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 2/3] xfs: refine the allocation stack switch
Date: Fri, 11 Jul 2014 08:33:53 -0400 [thread overview]
Message-ID: <20140711123352.GB3077@laptop.bfoster> (raw)
In-Reply-To: <1405034779-2028-3-git-send-email-david@fromorbit.com>
On Fri, Jul 11, 2014 at 09:26:18AM +1000, Dave Chinner wrote:
> From: Dave Chinner <dchinner@redhat.com>
>
...
>
> Signed-off-by: Dave Chinner <dchinner@redhat.com>
> ---
> fs/xfs/xfs_bmap.c | 4 +--
> fs/xfs/xfs_bmap_util.c | 43 --------------------------
> fs/xfs/xfs_bmap_util.h | 15 +++++----
> fs/xfs/xfs_btree.c | 84 ++++++++++++++++++++++++++++++++++++++++++++++++--
> 4 files changed, 91 insertions(+), 55 deletions(-)
>
...
> diff --git a/fs/xfs/xfs_bmap_util.h b/fs/xfs/xfs_bmap_util.h
> index 935ed2b..91df8e9 100644
> --- a/fs/xfs/xfs_bmap_util.h
> +++ b/fs/xfs/xfs_bmap_util.h
> @@ -50,12 +50,13 @@ struct xfs_bmalloca {
> xfs_extlen_t total; /* total blocks needed for xaction */
> xfs_extlen_t minlen; /* minimum allocation size (blocks) */
> xfs_extlen_t minleft; /* amount must be left after alloc */
> - char eof; /* set if allocating past last extent */
> - char wasdel; /* replacing a delayed allocation */
> - char userdata;/* set if is user data */
> - char aeof; /* allocated space at eof */
> - char conv; /* overwriting unwritten extents */
> - char stack_switch;
> + bool eof; /* set if allocating past last extent */
> + bool wasdel; /* replacing a delayed allocation */
> + bool userdata;/* set if is user data */
> + bool aeof; /* allocated space at eof */
> + bool conv; /* overwriting unwritten extents */
> + bool stack_switch;
> + bool kswapd; /* work being done for kswapd */
Neither stack_switch nor kswapd are used any longer. Removal of
stack_switch means that the XFS_BMAPI_STACK_SWITCH flag can go away as
well.
> int flags;
> struct completion *done;
> struct work_struct work;
> @@ -65,8 +66,6 @@ struct xfs_bmalloca {
> int xfs_bmap_finish(struct xfs_trans **tp, struct xfs_bmap_free *flist,
> int *committed);
> int xfs_bmap_rtalloc(struct xfs_bmalloca *ap);
> -int xfs_bmapi_allocate(struct xfs_bmalloca *args);
> -int __xfs_bmapi_allocate(struct xfs_bmalloca *args);
> int xfs_bmap_eof(struct xfs_inode *ip, xfs_fileoff_t endoff,
> int whichfork, int *eof);
> int xfs_bmap_count_blocks(struct xfs_trans *tp, struct xfs_inode *ip,
> diff --git a/fs/xfs/xfs_btree.c b/fs/xfs/xfs_btree.c
> index bf810c6..61168e3 100644
> --- a/fs/xfs/xfs_btree.c
> +++ b/fs/xfs/xfs_btree.c
> @@ -33,6 +33,7 @@
> #include "xfs_error.h"
> #include "xfs_trace.h"
> #include "xfs_cksum.h"
> +#include "xfs_alloc.h"
>
> /*
> * Cursor allocation zone.
> @@ -2322,8 +2323,8 @@ error1:
> * Return new block number and the key to its first
> * record (to be inserted into parent).
> */
> -STATIC int /* error */
> -xfs_btree_split(
> +int /* error */
> +__xfs_btree_split(
Looks like this can remain static. The rest looks Ok to me, but I'll run
some tests too.
Brian
> struct xfs_btree_cur *cur,
> int level,
> union xfs_btree_ptr *ptrp,
> @@ -2503,6 +2504,85 @@ error0:
> return error;
> }
>
> +struct xfs_btree_split_args {
> + struct xfs_btree_cur *cur;
> + int level;
> + union xfs_btree_ptr *ptrp;
> + union xfs_btree_key *key;
> + struct xfs_btree_cur **curp;
> + int *stat; /* success/failure */
> + int result;
> + bool kswapd; /* allocation in kswapd context */
> + struct completion *done;
> + struct work_struct work;
> +};
> +
> +/*
> + * Stack switching interfaces for allocation
> + */
> +static void
> +xfs_btree_split_worker(
> + struct work_struct *work)
> +{
> + struct xfs_btree_split_args *args = container_of(work,
> + struct xfs_btree_split_args, work);
> + unsigned long pflags;
> + unsigned long new_pflags = PF_FSTRANS;
> +
> + /*
> + * we are in a transaction context here, but may also be doing work
> + * in kswapd context, and hence we may need to inherit that state
> + * temporarily to ensure that we don't block waiting for memory reclaim
> + * in any way.
> + */
> + if (args->kswapd)
> + new_pflags |= PF_MEMALLOC | PF_SWAPWRITE | PF_KSWAPD;
> +
> + current_set_flags_nested(&pflags, new_pflags);
> +
> + args->result = __xfs_btree_split(args->cur, args->level, args->ptrp,
> + args->key, args->curp, args->stat);
> + complete(args->done);
> +
> + current_restore_flags_nested(&pflags, new_pflags);
> +}
> +
> +/*
> + * BMBT split requests often come in with little stack to work on. Push
> + * them off to a worker thread so there is lots of stack to use. For the other
> + * btree types, just call directly to avoid the context switch overhead here.
> + */
> +STATIC int /* error */
> +xfs_btree_split(
> + struct xfs_btree_cur *cur,
> + int level,
> + union xfs_btree_ptr *ptrp,
> + union xfs_btree_key *key,
> + struct xfs_btree_cur **curp,
> + int *stat) /* success/failure */
> +{
> + struct xfs_btree_split_args args;
> + DECLARE_COMPLETION_ONSTACK(done);
> +
> + if (cur->bc_btnum != XFS_BTNUM_BMAP)
> + return __xfs_btree_split(cur, level, ptrp, key, curp, stat);
> +
> + args.cur = cur;
> + args.level = level;
> + args.ptrp = ptrp;
> + args.key = key;
> + args.curp = curp;
> + args.stat = stat;
> + args.done = &done;
> + args.kswapd = current_is_kswapd();
> + INIT_WORK_ONSTACK(&args.work, xfs_btree_split_worker);
> + queue_work(xfs_alloc_wq, &args.work);
> + wait_for_completion(&done);
> + destroy_work_on_stack(&args.work);
> + return args.result;
> +}
> +
> +
> /*
> * Copy the old inode root contents into a real block and make the
> * broot point to it.
> --
> 2.0.0
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-07-11 12:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 23:26 [PATCH 0/3] xfs: regression fixes for 3.16-rc5 Dave Chinner
2014-07-10 23:26 ` [PATCH 1/3] Revert "xfs: block allocation work needs to be kswapd aware" Dave Chinner
2014-07-11 12:32 ` Brian Foster
2014-07-10 23:26 ` [PATCH 2/3] xfs: refine the allocation stack switch Dave Chinner
2014-07-11 12:33 ` Brian Foster [this message]
2014-07-11 21:57 ` Dave Chinner
2014-07-10 23:26 ` [PATCH 3/3] xfs: null unused quota inodes when quota is on Dave Chinner
2014-07-11 13:15 ` Brian Foster
2014-07-11 22:00 ` Dave Chinner
2014-07-11 15:22 ` Arkadiusz Miśkiewicz
2014-07-11 15:30 ` Arkadiusz Miśkiewicz
2014-07-14 0:58 ` Dave Chinner
-- strict thread matches above, loose matches on Subject: below --
2014-07-14 4:48 [PATCH 0/3, V2] xfs; fixes for 3.16-rc5 Dave Chinner
2014-07-14 4:48 ` [PATCH 2/3] xfs: refine the allocation stack switch Dave Chinner
2014-07-14 12:02 ` 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=20140711123352.GB3077@laptop.bfoster \
--to=bfoster@redhat.com \
--cc=david@fromorbit.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