| To: | linux-xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: vim file write mode on journaling fs. |
| From: | Colin Walters <walters@xxxxxxxxxxxxxxxxxx> |
| Date: | Sun, 12 Aug 2001 13:37:22 -0400 |
| In-reply-to: | <200108112126.f7BLQWe26468@xxxxxxxxxxxxxxxxxxxx> (Steve Lord's message of "Sat, 11 Aug 2001 16:26:32 -0500") |
| Mail-followup-to: | linux-xfs@xxxxxxxxxxx |
| Organization: | The Ohio State University Dept. of Computer and Info. Science |
| References: | <200108111848.f7BIm1704198@xxxxxxxxxxxxx> <200108112126.f7BLQWe26468@xxxxxxxxxxxxxxxxxxxx> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
| User-agent: | Gnus/5.090004 (Oort Gnus v0.04) Emacs/21.0.104 (powerpc-debian-linux-gnu) |
Steve Lord <lord@xxxxxxx> writes: > 2. An individual thread doing a write in XFS has no way of knowing > or predicting what else may just of happened, or be about to > happen on the system. You cannot say 'I will write my data now > because the system is idle', there may be a couple of Gbytes of > I/O about to come in from another source. Why couldn't the kernel keep some statistics about disk usage, and use those to make an educated guess as to whether or not we should write out the data immediately? I appreciate that XFS can deal with gigabytes of I/O, but such an event is very unlikely on my laptop :) |
| Previous by Date: | Re[2]: vim file write mode on journaling fs., Keith Matthews |
|---|---|
| Next by Date: | Re: vim file write mode on journaling fs., Eric Sandeen |
| Previous by Thread: | Re[2]: vim file write mode on journaling fs., Keith Matthews |
| Next by Thread: | Re: vim file write mode on journaling fs., Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |