From: Martin Knoblauch <spamtrap@knobisoft.de>
To: Fengguang Wu <wfg@mail.ustc.edu.cn>,
Martin Knoblauch <spamtrap@knobisoft.de>
Cc: linux-kernel@vger.kernel.org,
Peter zijlstra <a.p.zijlstra@chello.nl>,
mingo@redhat.com
Subject: Re: Understanding I/O behaviour - next try
Date: Wed, 29 Aug 2007 02:22:47 -0700 (PDT) [thread overview]
Message-ID: <377365.93295.qm@web32603.mail.mud.yahoo.com> (raw)
In-Reply-To: <388376840.29283@ustc.edu.cn>
--- Fengguang Wu <wfg@mail.ustc.edu.cn> wrote:
> On Wed, Aug 29, 2007 at 01:15:45AM -0700, Martin Knoblauch wrote:
> >
> > --- Fengguang Wu <wfg@mail.ustc.edu.cn> wrote:
> >
> > > You are apparently running into the sluggish kupdate-style
> writeback
> > > problem with large files: huge amount of dirty pages are getting
> > > accumulated and flushed to the disk all at once when dirty
> background
> > > ratio is reached. The current -mm tree has some fixes for it, and
> > > there are some more in my tree. Martin, I'll send you the patch
> if
> > > you'd like to try it out.
> > >
> > Hi Fengguang,
> >
> > Yeah, that pretty much describes the situation we end up. Although
> > "sluggish" is much to friendly if we hit the situation :-)
> >
> > Yes, I am very interested to check out your patch. I saw your
> > postings on LKML already and was already curious. Any chance you
> have
> > something agains 2.6.22-stable? I have reasons not to move to -23
> or
> > -mm.
>
> Well, they are a dozen patches from various sources. I managed to
> back-port them. It compiles and runs, however I cannot guarantee
> more...
>
Thanks. I understand the limited scope of the warranty :-) I will give
it a spin today.
> > > > Another thing I saw during my tests is that when writing to
> NFS,
> > > the
> > > > "dirty" or "nr_dirty" numbers are always 0. Is this a
> conceptual
> > > thing,
> > > > or a bug?
> > >
> > > What are the nr_unstable numbers?
> > >
> >
> > Ahh. Yes, they go up to 80-90k pages. Comparable to the nr_dirty
> > numbers for the disk case. Good to know.
> >
> > For NFS, the nr_writeback numbers seem surprisingly high. They
> also go
> > to 80-90k (pages ?). In the disk case they rarely go over 12k.
>
> Maybe the difference of throttling one single 'cp' and a dozen
> 'nfsd'?
>
No "nfsd" running on that box. It is just a client.
Cheers
Martin
------------------------------------------------------
Martin Knoblauch
email: k n o b i AT knobisoft DOT de
www: http://www.knobisoft.de
next prev parent reply other threads:[~2007-08-29 9:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-28 15:53 Martin Knoblauch
[not found] ` <20070829013858.GA7721@mail.ustc.edu.cn>
2007-08-29 1:38 ` Fengguang Wu
2007-08-29 8:15 ` Martin Knoblauch
[not found] ` <20070829084039.GA32016@mail.ustc.edu.cn>
2007-08-29 8:40 ` Fengguang Wu
2007-08-29 9:22 ` Martin Knoblauch [this message]
2007-09-13 14:17 ` Peter Zijlstra
2007-08-29 9:48 ` Jens Axboe
2007-08-29 14:26 ` Martin Knoblauch
2007-08-30 10:50 ` Martin Knoblauch
2007-08-29 16:25 ` Chuck Ebbert
2007-08-29 21:43 ` Martin Knoblauch
[not found] <fa.tV0SjP5wHRgCEzqJw2C8w4+Fh90@ifi.uio.no>
[not found] ` <fa.NN9klzYbZhoZ+YoOWgrMeLtzlHE@ifi.uio.no>
2007-08-29 14:27 ` Robert Hancock
2007-08-30 10:26 ` Martin Knoblauch
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=377365.93295.qm@web32603.mail.mud.yahoo.com \
--to=spamtrap@knobisoft.de \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=wfg@mail.ustc.edu.cn \
/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
Powered by JetHome