From: David Chinner <dgc@sgi.com>
To: Lachlan McIlroy <lachlan@sgi.com>
Cc: "Török Edwin" <edwintorok@gmail.com>,
"Arjan van de Ven" <arjan@linux.intel.com>,
xfs@oss.sgi.com
Subject: Re: Marking inode dirty latency > 1000 msec on XFS!
Date: Fri, 22 Feb 2008 18:16:08 +1100 [thread overview]
Message-ID: <20080222071608.GT155407@sgi.com> (raw)
In-Reply-To: <47BE6C5C.2000605@sgi.com>
On Fri, Feb 22, 2008 at 05:31:56PM +1100, Lachlan McIlroy wrote:
> Török Edwin wrote:
> >FWIW, this is a slow laptop hdd (5400 rpm, ST96812AS), but latency of 1
> >second is still big.
> >
> >Are there any settings I can tweak to reduce latency?
> Um, not that I am aware of.
Try using a filesystem that has lazy-count enabled.
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2008-02-22 7:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 18:44 Marking inode dirty latency > 1000 msec on XFS! Török Edwin
2008-02-22 6:31 ` Lachlan McIlroy
2008-02-22 7:16 ` David Chinner [this message]
2008-02-22 8:40 ` Török Edwin
2008-02-22 8:59 ` Török Edwin
2008-02-22 10:20 ` Török Edwin
2008-02-23 0:06 ` David Chinner
2008-02-23 9:41 ` Török Edwin
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=20080222071608.GT155407@sgi.com \
--to=dgc@sgi.com \
--cc=arjan@linux.intel.com \
--cc=edwintorok@gmail.com \
--cc=lachlan@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