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:
signature.asc
Description: This is a digitally signed message part
- References:
- Re: Understanding I/O behaviour - next try
- From: Martin Knoblauch <[email protected]>
- Re: Understanding I/O behaviour - next try
- Prev by Date: Re: [CORRECTION][PATCH] Fix a potential NULL pointer dereference in uli526x_interrupt() in drivers/net/tulip/uli526x.c
- Next by Date: Re: [PATCH] 9p: attach-per-user
- Previous by thread: Re: Understanding I/O behaviour - next try
- Next by thread: Re: Understanding I/O behaviour - next try
- Index(es):