mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: spamtrap@knobisoft.de
Cc: Fengguang Wu <wfg@mail.ustc.edu.cn>,
	linux-kernel@vger.kernel.org, mingo@redhat.com
Subject: Re: Understanding I/O behaviour - next try
Date: Thu, 13 Sep 2007 16:17:37 +0200	[thread overview]
Message-ID: <1189693057.21778.234.camel@twins> (raw)
In-Reply-To: <353439.71100.qm@web32603.mail.mud.yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 966 bytes --]

On Wed, 2007-08-29 at 01:15 -0700, Martin Knoblauch wrote:

> > >  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?

NFS has the concept of unstable storage, that is a state where it is
agreed the page has been transferred to the remote server, but has not
yet been written to disk.

>  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.

see: /proc/sys/fs/nfs/nfs_congestion_kb

That is the limit for when the nfs BDI is marked congested, so
nfs_writeout + nfs_unstable <= nfs_congestion_kb

The nfs_dirty always being 0 just means that pages very quickly start
their writeout cycle.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2007-09-13 14:17 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
2007-09-13 14:17       ` Peter Zijlstra [this message]
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=1189693057.21778.234.camel@twins \
    --to=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=spamtrap@knobisoft.de \
    --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