From: tinguely@sgi.com
To: xfs@oss.sgi.com
Subject: [PATCH 1/3] xfs: restrict allocate worker to x86_64
Date: Wed, 19 Sep 2012 11:31:34 -0500 [thread overview]
Message-ID: <20120919163145.367256258@sgi.com> (raw)
In-Reply-To: 20120919163133.097340199@sgi.com
[-- Attachment #1: 1-3-xfs-restrict_allocate_worker.patch --]
[-- Type: text/plain, Size: 1459 bytes --]
Restrict the allocation worker to X86_64 machines. This will improve
performance on non-X86-64 machines and avoid the AGF buffer hang.
Signed-off-by: Mark Tinguely <tinguely@sgi.com>
---
fs/xfs/xfs_alloc.c | 11 +++++++++++
1 file changed, 11 insertions(+)
Index: b/fs/xfs/xfs_alloc.c
===================================================================
--- a/fs/xfs/xfs_alloc.c
+++ b/fs/xfs/xfs_alloc.c
@@ -2417,6 +2417,7 @@ error0:
return error;
}
+#if defined(CONFIG_X86_64)
static void
xfs_alloc_vextent_worker(
struct work_struct *work)
@@ -2433,6 +2434,7 @@ xfs_alloc_vextent_worker(
current_restore_flags_nested(&pflags, PF_FSTRANS);
}
+#endif
/*
* Data allocation requests often come in with little stack to work on. Push
@@ -2444,6 +2446,7 @@ int
xfs_alloc_vextent(
struct xfs_alloc_arg *args)
{
+#if defined(CONFIG_X86_64)
DECLARE_COMPLETION_ONSTACK(done);
if (!args->userdata)
@@ -2455,6 +2458,14 @@ xfs_alloc_vextent(
queue_work(xfs_alloc_wq, &args->work);
wait_for_completion(&done);
return args->result;
+#else
+ /* The allocation worker is needed by the i386_64.
+ * Do not use the worker for other platforms. This will
+ * allow those platforms avoid the performance hit and
+ * the potential AGF buffer deadlock issue.
+ */
+ return __xfs_alloc_vextent(args);
+#endif
}
/*
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-09-19 16:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 16:31 [PATCH 0/3] xfs: allocation worker causes freelist buffer lock hang tinguely
2012-09-19 16:31 ` tinguely [this message]
2012-09-19 21:54 ` [PATCH 1/3] xfs: restrict allocate worker to x86_64 Dave Chinner
2012-09-20 17:37 ` Mark Tinguely
2012-09-24 17:37 ` Ben Myers
2012-09-25 0:14 ` Dave Chinner
2012-09-19 16:31 ` [PATCH 2/3] xfs: move allocate worker tinguely
2012-09-19 16:31 ` [PATCH 3/3] xfs: zero allocation_args on the kernel stack tinguely
2012-09-19 23:41 ` Dave Chinner
2012-09-20 18:16 ` [PATCH 3/3 v2] " Mark Tinguely
2012-09-25 20:20 ` Ben Myers
2012-10-18 22:52 ` Ben Myers
2012-09-19 23:34 ` [PATCH 0/3] xfs: allocation worker causes freelist buffer lock hang Dave Chinner
2012-09-20 13:49 ` Mark Tinguely
2012-09-24 13:25 ` Dave Chinner
2012-09-24 17:11 ` Ben Myers
2012-09-24 18:09 ` Mark Tinguely
2012-09-25 0:56 ` Dave Chinner
2012-09-25 15:14 ` Mark Tinguely
2012-09-25 22:01 ` Dave Chinner
2012-09-26 14:14 ` Mark Tinguely
2012-09-26 23:41 ` Dave Chinner
2012-09-27 20:10 ` Mark Tinguely
2012-09-28 3:08 ` Dave Chinner
2012-10-01 22:10 ` [PATCH 0/3] xfs: allocation worker causes freelist buffer lock Mark Tinguely
2012-10-01 23:10 ` Dave Chinner
2012-09-27 22:48 ` [PATCH 0/3] xfs: allocation worker causes freelist buffer lock hang Ben Myers
2012-09-27 23:17 ` Mark Tinguely
2012-09-27 23:27 ` Mark Tinguely
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=20120919163145.367256258@sgi.com \
--to=tinguely@sgi.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