From: Brian Foster <bfoster@redhat.com>
To: xfs@oss.sgi.com
Subject: [PATCH v3 0/2] xfs: split up xfslogd global workqueue
Date: Thu, 13 Nov 2014 14:23:59 -0500 [thread overview]
Message-ID: <1415906641-43587-1-git-send-email-bfoster@redhat.com> (raw)
I've broken this up into two patches because the bugfix is easy (patch
1) and I don't want to rework it for the purpose of refactoring usage of
the queue. Patch 1 is a straightforward, tested and backportable fix for
a specific problem and it's no more difficult to refactor queue usage
from a per-mount queue than from a single global queue.
The metadata/log buffer I/O separation is not as straightforward as
defining separate queues. We need to also define a mechanism to split
the completions across multiple queues within the buffer code. The ioend
code does this for the data/unwritten queues via the io type. There are
a few different ways we can go from here with regard to buffers. For
example:
- Define per-buftarg workqueues and configure them appropriately for
data and log devices.
- Split buf completion processing based on a buffer flag (or some other
identification).
- Continue using a single queue (per-mount) for metadata/log
completions.
The first approach introduces variance in that the separation only
occurs with separate data and log devices. This is not ideal and doesn't
seem worthwhile to me. It doesn't change anything in the common case and
introduces a new regression vector for the uncommon case.
The second approach is implemented by the 2/2 RFC of this series using
the XBF_SYNCIO flag simply because it only appears to be used by log
buffers at the moment. If we take this approach, should we define
something like an XBF_LOGIO or XBF_HIGHPRI flag?
The third approach simply involves dropping patch 2/2 and using the
per-mount queue as we use the global queue today.
Brian
v3:
- Split bug fix and buf/log I/O split into separate patches.
- Rename xfslogd workqueue to xfs-buf.
v2: http://oss.sgi.com/archives/xfs/2014-11/msg00164.html
- Rename xfslogd workqueue to xfs-iodone.
v1: http://oss.sgi.com/archives/xfs/2014-10/msg00539.html
Brian Foster (2):
xfs: replace global xfslogd wq with per-mount wq
xfs: split metadata and log buffer completion to separate workqueues
fs/xfs/xfs_buf.c | 19 ++++++++-----------
fs/xfs/xfs_mount.h | 1 +
fs/xfs/xfs_super.c | 12 ++++++++++--
3 files changed, 19 insertions(+), 13 deletions(-)
--
1.8.3.1
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2014-11-13 19:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 19:23 Brian Foster [this message]
2014-11-13 19:24 ` [PATCH v3 1/2] xfs: replace global xfslogd wq with per-mount wq Brian Foster
2014-11-28 2:49 ` Dave Chinner
2014-11-13 19:24 ` [PATCH RFC v3 2/2] xfs: split metadata and log buffer completion to separate workqueues Brian Foster
2014-11-28 2:48 ` Dave Chinner
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=1415906641-43587-1-git-send-email-bfoster@redhat.com \
--to=bfoster@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