From: David Chinner <dgc@sgi.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
linux-fsdevel@vger.kernel.org
Subject: Re: kupdate weirdness
Date: Thu, 2 Aug 2007 11:53:18 +1000 [thread overview]
Message-ID: <20070802015318.GM12413810@sgi.com> (raw)
In-Reply-To: <E1IGL4G-00088R-00@dorka.pomaz.szeredi.hu>
On Wed, Aug 01, 2007 at 10:45:16PM +0200, Miklos Szeredi wrote:
> The following strange behavior can be observed:
>
> 1. large file is written
> 2. after 30 seconds, nr_dirty goes down by 1024
> 3. then for some time (< 30 sec) nothing happens (disk idle)
> 4. then nr_dirty again goes down by 1024
> 5. repeat from 3. until whole file is written
>
> So basically a 4Mbyte chunk of the file is written every 30 seconds.
> I'm quite sure this is not the intended behavior.
>
> The reason seems to be that __sync_single_inode() will move the
> partially written inode from s_io onto s_dirty, and sync_sb_inode()
> will not splice it back onto s_io until the rest of the inodes on s_io
> has been processed.
It's been doing this for a long time.
http://marc.info/?l=linux-kernel&m=113919849421679&w=2
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
prev parent reply other threads:[~2007-08-02 1:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 20:45 kupdate weirdness Miklos Szeredi
2007-08-01 21:14 ` Andrew Morton
2007-08-02 15:52 ` Miklos Szeredi
2007-08-02 19:18 ` Andrew Morton
2007-08-02 19:35 ` Miklos Szeredi
[not found] ` <1186091062.11797.34.camel@lappy>
2007-08-03 6:43 ` per bdi dirty balancing (was Re: kupdate weirdness) Miklos Szeredi
2007-08-03 7:15 ` Peter Zijlstra
2007-08-03 7:41 ` Miklos Szeredi
2007-08-02 1:53 ` David Chinner [this message]
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=20070802015318.GM12413810@sgi.com \
--to=dgc@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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