Linux-kernel mailing list archive 1997-11,: Re: More on 2.1.65 slowdown (disc thrashing)

# Re: More on 2.1.65 slowdown (disc thrashing)

Rik van Riel (H.H.vanRiel@fys.ruu.nl)
Mon, 24 Nov 1997 13:21:34 +0100 (MET)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Jes Degn Soerensen: "Re: TTY changes to 2.1.65"
- Previous message: Rik van Riel: "Re: More on 2.1.65 slowdown (disc thrashing)"

On 21 Nov 1997, Andi Kleen wrote:

> syslogd is the most prominent user of fsync() and log files tend to grow
> big..

Also, they tend to be _appended_ to... Usually only one block
would need to be synced. Couldn't there be a way of detecting
this special case.

Another strategy might be to just walk though the buffer cache
and sync all buffers associated with that file... A linear mem
walk is quite fast, and the test is very fast. We just need to
look at the 'page->inode' and see if this is the inode we want
to flush.

Rik.

----------
Send Linux memory-management wishes to me: I'm currently looking
for something to hack...

- Next message: Jes Degn Soerensen: "Re: TTY changes to 2.1.65"
- Previous message: Rik van Riel: "Re: More on 2.1.65 slowdown (disc thrashing)"