On 4/28/07, Mikulas Patocka <[email protected]> wrote:
I most wonder, why vim fsyncs its swapfile regularly (blocking typing during that) and doesn't fsync the resulting file on :w :-/
Never seen this. Why would fsync block typing unless vim was doing disk IO for every keystroke? Lee - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [ext3][kernels >= 2.6.20.7 at least] KDE going comatose when FS is under heavy write load (massive starvation)
- From: Mikulas Patocka <[email protected]>
- Re: [ext3][kernels >= 2.6.20.7 at least] KDE going comatose when FS is under heavy write load (massive starvation)
- From: Mark Lord <[email protected]>
- Re: [ext3][kernels >= 2.6.20.7 at least] KDE going comatose when FS is under heavy write load (massive starvation)
- References:
- [ext3][kernels >= 2.6.20.7 at least] KDE going comatose when FS is under heavy write load (massive starvation)
- From: Mike Galbraith <[email protected]>
- Re: [ext3][kernels >= 2.6.20.7 at least] KDE going comatose when FS is under heavy write load (massive starvation)
- From: Andrew Morton <[email protected]>
- Re: [ext3][kernels >= 2.6.20.7 at least] KDE going comatose when FS is under heavy write load (massive starvation)
- From: Mikulas Patocka <[email protected]>
- [ext3][kernels >= 2.6.20.7 at least] KDE going comatose when FS is under heavy write load (massive starvation)
- Prev by Date: Re: [PROBLEM] Bonding driver in linux-2.6.21-rc6-mm1
- Next by Date: Re: Flaws with "UIO: Add the User IO core code"
- Previous by thread: Re: [ext3][kernels >= 2.6.20.7 at least] KDE going comatose when FS is under heavy write load (massive starvation)
- Next by thread: Re: [ext3][kernels >= 2.6.20.7 at least] KDE going comatose when FS is under heavy write load (massive starvation)
- Index(es):
 |