From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: ensure log covering transactions are synchronous
Date: Tue, 4 Jan 2011 03:21:30 -0500 [thread overview]
Message-ID: <20110104082130.GA29016@infradead.org> (raw)
In-Reply-To: <1294116569-15052-1-git-send-email-david@fromorbit.com>
Ok, my fault for asking to avoid stalling xfssyncd.
> Fix this by making the log covering transaction synchronous. To
> avoid additional log force from xfssyncd, make the log covering
> transaction take the place of the existing log force in the xfssyncd
> background sync process.
This also looks correct to me. We replace a force with a lsn-force, but
given that we just started the transaction those should be equivalent.
Reviewed-by: Christoph Hellwig <hch@lst.de>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-01-04 8:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 4:49 [PATCH] xfs: ensure log covering transactions are synchronous Dave Chinner
2011-01-04 8:21 ` Christoph Hellwig [this message]
2011-01-05 2:01 ` Alex Elder
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=20110104082130.GA29016@infradead.org \
--to=hch@infradead.org \
--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