From: Andi Kleen <andi@firstfloor.org>
To: David Chinner <dgc@sgi.com>
Cc: xfs-oss <xfs@oss.sgi.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/9]: Reduce Log I/O latency
Date: Thu, 22 Nov 2007 01:49:25 +0100 [thread overview]
Message-ID: <p73oddnhzoq.fsf@bingen.suse.de> (raw)
In-Reply-To: <20071122003339.GH114266761__34694.2978365861$1195691722$gmane$org@sgi.com> (David Chinner's message of "Thu\, 22 Nov 2007 11\:33\:39 +1100")
David Chinner <dgc@sgi.com> writes:
> To ensure that log I/O is issued as the highest priority I/O, set
> the I/O priority of the log I/O to the highest possible. This will
> ensure that log I/O is not held up behind bulk data or other
> metadata I/O as delaying log I/O can pause the entire transaction
> subsystem. Introduce a new buffer flag to allow us to tag the log
> buffers so we can discrimiate when issuing the I/O.
Won't that possible disturb other RT priority users that do not need
log IO (e.g. working on preallocated files)? Seems a little
dangerous.
I suspect you want a "higher than bulk but lower than RT" priority
for this really unless there is any block RT priority task waiting
for log IO (but keeping track of the later might be tricky)
-Andi
next parent reply other threads:[~2007-11-22 0:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071122003339.GH114266761__34694.2978365861$1195691722$gmane$org@sgi.com>
2007-11-22 0:49 ` Andi Kleen [this message]
2007-11-22 1:12 ` [PATCH 2/9]: Reduce Log I/O latency David Chinner
2007-11-22 2:57 ` Matt Mackall
2007-11-22 3:41 ` David Chinner
2007-11-22 7:25 ` Matt Mackall
2007-11-22 10:31 ` David Chinner
2007-11-22 18:10 ` Matt Mackall
2007-11-22 22:29 ` David Chinner
2007-11-22 23:09 ` David Chinner
2007-11-23 0:21 ` Matt Mackall
2007-11-23 0:20 ` Matt Mackall
2007-11-22 3:28 ` Stewart Smith
2007-11-22 12:06 ` Andi Kleen
2007-11-22 13:15 ` David Chinner
2007-11-23 2:53 ` Andi Kleen
2007-11-23 4:03 ` David Chinner
2007-11-23 12:01 ` Andi Kleen
2007-11-24 18:43 ` Matt Mackall
2007-11-22 0:33 David Chinner
2007-11-26 2:11 ` Lachlan McIlroy
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=p73oddnhzoq.fsf@bingen.suse.de \
--to=andi@firstfloor.org \
--cc=dgc@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--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