From: Brian Foster <bfoster@redhat.com>
To: xfs@oss.sgi.com
Subject: [PATCH v2 0/2] serialize unmount against new buffer I/O
Date: Fri, 15 Jul 2016 14:35:32 -0400 [thread overview]
Message-ID: <1468607734-3174-1-git-send-email-bfoster@redhat.com> (raw)
v2:
- Drop patch 1. Use existing flags argument to set NO_IOACCT and fold
into patch 2.
- Clear IN_FLIGHT status on marking a buffer stale.
- Add IN_FLIGHT to tracepoint flags string list.
v1: http://oss.sgi.com/pipermail/xfs/2016-July/050148.html
Brian Foster (2):
xfs: exclude never-released buffers from buftarg I/O accounting
xfs: track and serialize in-flight async buffers against unmount
fs/xfs/xfs_buf.c | 168 +++++++++++++++++++++++++++++++++++++++--------------
fs/xfs/xfs_buf.h | 7 ++-
fs/xfs/xfs_log.c | 5 +-
fs/xfs/xfs_mount.c | 10 ++--
4 files changed, 141 insertions(+), 49 deletions(-)
--
2.5.5
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2016-07-15 18:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 18:35 Brian Foster [this message]
2016-07-15 18:35 ` [PATCH v2 1/2] xfs: exclude never-released buffers from buftarg I/O accounting Brian Foster
2016-07-15 18:35 ` [PATCH v2 2/2] xfs: track and serialize in-flight async buffers against unmount 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=1468607734-3174-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